# CVE-2026-24125: Path Traversal in @tinacms/graphql

> Attackers can escape collection directories via GraphQL mutations to read or modify arbitrary files, affecting TinaCMS users.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-2238-xc5r-v9hj

## What is CVE-2026-24125?

CVE-2026-24125 is a medium-severity path traversal vulnerability in @tinacms graphql, published on 12 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Tina is a headless content management system. Prior to 2.1.2, 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. This vulnerability is fixed in 2.1.2.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-24125?

2 open source packages ship an affected version, including @tinacms/graphql. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@tinacms/graphql` | npm | All versions | 2.1.2 |
| `@tinacms/graphql` | npm | All versions | 2.1.2 |

Products: Ssw Tinacms\/Graphql.

## How do I fix CVE-2026-24125?

Upgrade @tinacms/graphql to 2.1.2 or later.

## Is CVE-2026-24125 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24125 exists.

## Other vulnerabilities in @tinacms graphql

- [CVE-2026-33949](https://insights.sbomify.com/CVE-2026-33949/): @tinacms/graphql has Path Traversal that leads to overwrite of arbitrary files (high 8.1)
- [CVE-2026-34604](https://insights.sbomify.com/CVE-2026-34604/): @tinacms/graphql's `FilesystemBridge` Path Validation Can Be Bypassed via Symlinks or Junctions (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24125 and fix it if it is affected.

What it is: CVE-2026-24125 is a medium-severity path traversal vulnerability in @tinacms graphql, published on 12 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24125 exists.

Affected packages and fixed versions:
- @tinacms/graphql (npm): affected all versions; fixed in 2.1.2
- @tinacms/graphql (npm): affected all versions; fixed in 2.1.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24125/ (Markdown: https://insights.sbomify.com/CVE-2026-24125/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24125
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24125
- OSV: https://osv.dev/vulnerability/CVE-2026-24125

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24125/
Summaries are generated and may contain mistakes; the official description above is the record.