Skip to main content
Menu
CVEs

CVE

TinaCMS GraphQL path traversal via symlinks in FilesystemBridge

CVE-2026-129861EUVD-2026-126459GHSA-PQM4-95X4-2G57

CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N

6.0MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported
Published
Last modified
Reference
Last checked
24/100 · provisional
83% of @tinacms/graphql downloads last week were affected versions (46.4K).npm, 56.2K downloads in the last 7 days, read Nov 15, 2026
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

The @tinacms/graphql package has a path traversal flaw that lets an authenticated user write files outside the content root by following pre-existing dangling symlinks. An attacker with low-privilege access can exploit it remotely through the GraphQL API by creating documents that target such a symlink, writing controlled content to server-writable locations.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

@tinacms/graphql 2.2.2 through 4.1.0 contains a path traversal vulnerability that allows authenticated users to write files outside the content root by following pre-existing dangling symlinks. Attackers can create documents through the GraphQL API targeting a dangling symlink, bypassing assertWithinBase checks, to write controlled content such as authorized_keys to server-writable locations.

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Affects npm packages
  • Severity6/10CVSS 6.0
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 79 if added to CISA KEV
  • Would score about 74 if CISA's SSVC rates exploitation active
  • Would score about 43 if advisories confirm default setups are exposed

Impact

  • Widely used

    @tinacms/graphql has 58.4k weekly downloads.Source: npmjs.com

    7 packages depend on @tinacms/graphql.Source: deps.dev

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129861 (@tinacms/graphql 2.2.2 through 4.1.0 Path Traversal via Dangling Symlink in FilesystemBridge.put), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129861 (entry last updated 2026-11-16):
Affected:
- npm package @tinacms/graphql: from 2.2.2, through 4.1.0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129861 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129861 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/tinacms/tinacms/security/advisories/GHSA-g9c2-gf25-3x67
- https://github.com/tinacms/tinacms/blob/1f33e863f530921a447b832196dcb87efc2d9377/packages/@tinacms/graphql/src/database/bridge/filesystem.ts#L20-L27
- https://www.vulncheck.com/advisories/tinacms-graphql-2.2.2-through-4.1.0-path-traversal-via-dangling-symlink-in-filesystembridge-put
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129861
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129861"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • From 2.2.2 · through 4.1.0

    No fix released. The latest release, 4.1.0, is still affected.

Evidence 5

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Repository
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129861

Is CVE-2026-129861 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-129861?

@tinacms/graphql (npm): from 2.2.2 through 4.1.0.Source: cve.now feed data