CVE-2026-129861 · Package
NO FIX YET · SEE WHAT TO DO
Versions 2.2.2 through 4.1.0 of @tinacms/graphql let an authenticated user create documents that follow pre-existing dangling symlinks and write outside the content directory. A write such as an authorized_keys file to a server-writable path could lead to server takeover.
first public Mar 30, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Sites that run @tinacms/graphql in the 2.2.2 to 4.1.0 range and let authenticated users write content through the GraphQL API are exposed. Sites that only serve static builds or do not expose authenticated writes can skip it. The sources do not say whether dangling symlinks must already exist in the content root.
Not affected if auth-required, static-export
Who cares node, self-hosted, tinacms
npm ls @tinacms/graphql@tinacms/graphql to a version later than 4.1.0; the exact fixed version is unknown from these sources@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.
This page as .md · .json · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.