# CVE-2026-28792: Cross-Origin File Exfiltration via CORS Misconfiguration + Path Traversal in TinaCMS

> Attackers can read, write, and delete files on developer machines via a drive-by attack exploiting CORS and path traversal in TinaCMS CLI.

- **Severity:** Critical 9.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 12 Mar 2026
- **Updated:** 13 Mar 2026
- **Also known as:** GHSA-8pw3-9m7f-q734

## What is CVE-2026-28792?

CVE-2026-28792 is a critical path traversal vulnerability in @tinacms cli, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Tina is a headless content management system. Prior to 2.1.8 , the TinaCMS CLI dev server combines a permissive CORS configuration (Access-Control-Allow-Origin: *) with the path traversal vulnerability (previously reported) to enable a browser-based drive-by attack. A remote attacker can enumerate the filesystem, write arbitrary files, and delete arbitrary files on developer's machines by simply tricking them into visiting a malicious website while tinacms dev is running. This vulnerability is fixed in 2.1.8.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@tinacms/cli` | npm | All versions | 2.1.8 |
| `@tinacms/cli` | npm | All versions | 2.1.8 |

Products: Ssw Tinacms\/Cli.

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

Upgrade @tinacms/cli to 2.1.8 or later.

## Is CVE-2026-28792 being exploited?

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

## Other vulnerabilities in @tinacms cli

- [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)
- [CVE-2026-34603](https://insights.sbomify.com/CVE-2026-34603/): @tinacms/graphql's Media Endpoints Can Escape the Media Root via Symlinks or Junctions (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-28792 is a critical path traversal vulnerability in @tinacms cli, published on 12 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28792 exists.

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

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-28792/ (Markdown: https://insights.sbomify.com/CVE-2026-28792/index.md)
```

## Sources

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

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