# CVE-2026-34603: @tinacms/graphql's Media Endpoints Can Escape the Media Root via Symlinks or Junctions

> Attackers can escape the media root directory via symlinks to read, write, or delete files outside the intended scope in TinaCMS.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/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:** 1 Apr 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-g87c-r2jp-293w

## What is CVE-2026-34603?

CVE-2026-34603 is a high-severity path traversal vulnerability in tinacms, published on 1 Apr 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 version 2.2.2, @tinacms/cli recently added lexical path-traversal checks to the dev media routes, but the implementation still validates only the path string and does not resolve symlink or junction targets. If a link already exists under the media root, Tina accepts a path like pivot/written-from-media.txt as "inside" the media directory and then performs real filesystem operations through that link target. This allows out-of-root media listing and write access, and the same root cause also affects delete. This issue has been patched in version 2.2.2.

Weakness: CWE-59 (Improper Link Resolution Before File Access), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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.2.2 |
| `@tinacms/graphql` | npm | All versions | 2.2.2 |

Products: Ssw Tinacms\/Cli.

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

Upgrade @tinacms/graphql to 2.2.2 or later.

## Is CVE-2026-34603 being exploited?

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

## Other vulnerabilities in tinacms

- [CVE-2026-28792](https://insights.sbomify.com/CVE-2026-28792/): Cross-Origin File Exfiltration via CORS Misconfiguration + Path Traversal in TinaCMS (critical 9.7)
- [CVE-2023-25164](https://insights.sbomify.com/CVE-2023-25164/): Sensitive Information leak via Script File in TinaCMS (high 8.6)
- [CVE-2026-28793](https://insights.sbomify.com/CVE-2026-28793/): Path Traversal Leading to Arbitrary File Read, Write and Delete in TinaCMS (high 8.4)
- [CVE-2024-45391](https://insights.sbomify.com/CVE-2024-45391/): Tina search token leak via lock file in TinaCMS (high 7.5)
- [CVE-2026-28791](https://insights.sbomify.com/CVE-2026-28791/): Path Traversal in Media Upload Handle in Tina (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34603 is a high-severity path traversal vulnerability in tinacms, published on 1 Apr 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-34603 exists.

Affected packages and fixed versions:
- @tinacms/graphql (npm): affected all versions; fixed in 2.2.2
- @tinacms/graphql (npm): affected all versions; fixed in 2.2.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-34603/ (Markdown: https://insights.sbomify.com/CVE-2026-34603/index.md)
```

## Sources

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

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