@tinacms/graphql has a Path Traversal issue

Exploitation

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

CVSS

6.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

EPSS

• CVE-2026-24125: 0.45% estimated exploitation activity in the next 30 days; percentile 39.34 (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.

Description TinaCMS allows users to create, update, and delete content documents using relative file paths (relativePath, newRelativePath) via GraphQL mutations. Under certain conditions, these paths are combined with the collection path using path.join() without validating that the resolved path remains within the collection root directory. Because path.join() does not prevent directory traversal, paths containing ../ sequences can escape the intended directory boundary. Attack Vectors 1. File Creation: Create files outside the collection directory 2. File Move/Rename: Move existing files outside the collection 3. File Deletion: Delete files outside the collection 4. Folder Creation: Create folders outside the collection Impact An authenticated user with document mutation permissions can: - Create content files outside collection boundaries (subject to schema validation) - Move or rename files outside collection boundaries - Delete content files outside collection boundaries - Read…

Published by the source

12 Mar 2026, 17:50 UTC

Last modified by the source

14 Mar 2026, 06:26 UTC

Source last checked

26 Oct 2026, 12:46 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-2238-xc5r-v9hj

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-2238-xc5r-v9hj

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

# Patch Next advisory brief: CVE-2026-24125

Advisory: @tinacms/graphql has a Path Traversal issue
IDs: CVE-2026-24125, GHSA-2238-xc5r-v9hj
Record: https://patchnext.com/advisories/cve-2026-24125 (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: Medium (CVSS 6.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @tinacms/graphql 2.1.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @tinacms/graphql: affected <= 2.1.1; fixed in 2.1.2

## Suggested inspection (read-only)
- `npm ls @tinacms/graphql --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/graphql.
- 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-2238-xc5r-v9hj (OSV record GHSA-2238-xc5r-v9hj lists affected ranges: npm @tinacms/graphql >=0 <2.1.2 (fixed))
- Verified: https://github.com/advisories/GHSA-2238-xc5r-v9hj (GitHub-reviewed advisory GHSA-2238-xc5r-v9hj lists affected ranges: npm @tinacms/graphql >=0 <=2.1.1)

Commands are suggestions: review each one before running it.