Tina: Path Traversal in Media Upload Handle

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.4 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H

EPSS

• CVE-2026-28791: 0.34% estimated exploitation activity in the next 30 days; percentile 28.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Affected Package | Field | Value | |-------|-------| | Package | @tinacms/cli | | Version | 2.0.5 (latest at time of discovery) | | Vulnerable File | packages/@tinacms/cli/src/next/commands/dev-command/server/media.ts | | Vulnerable Lines | 42-43 | --- Summary A path traversal vulnerability (CWE-22) exists in the TinaCMS development server's media upload handler. The code at media.ts:42-43 joins user-controlled path segments using path.join() without validating that the resulting path stays within the intended media directory. This allows writing files to arbitrary locations on the filesystem. Attack Vector: Network (HTTP POST request) Impact: Arbitrary file write, potential Remote Code Execution --- Details Vulnerable Code Location File: packages/@tinacms/cli/src/next/commands/dev-command/server/media.ts Lines: 42-43 Root Cause The path.join() function resolves .. (parent directory) segments in the path. When the user-supplied path contains traversal sequences like…

Published by the source

12 Mar 2026, 18:32 UTC

Last modified by the source

14 Mar 2026, 05:56 UTC

Source last checked

26 Oct 2026, 12:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-5hxf-c7j4-279c

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-5hxf-c7j4-279c

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28791

Advisory: Tina: Path Traversal in Media Upload Handle
IDs: CVE-2026-28791, GHSA-5hxf-c7j4-279c
Record: https://patchnext.com/advisories/cve-2026-28791 (revision 2, source checked 26 Oct 2026, 12:46 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: tinacms 2.1.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm tinacms: affected < 2.1.7; fixed in 2.1.7

## Suggested inspection (read-only)
- `npm ls tinacms --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on tinacms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-5hxf-c7j4-279c (OSV record GHSA-5hxf-c7j4-279c lists affected ranges: npm tinacms >=0 <2.1.7 (fixed))
- Verified: https://github.com/advisories/GHSA-5hxf-c7j4-279c (GitHub-reviewed advisory GHSA-5hxf-c7j4-279c lists affected ranges: npm tinacms >=0 <2.1.7)

Commands are suggestions: review each one before running it.