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...
Product
tinacms graphql vulnerabilities
5 published CVES affecting tinacms graphql, from public sources (CVE.org, NVD, CISA KEV, FIRST EPSS, OSV).
- Total
- 5
- Critical
- 0
- High
- 4
- Medium
- 1
- Low
- 0
- Unscored
- 0
- CISA KEV
- 0
Latest tinacms graphql CVEs
Newest publication first
-
HighCVSS 8.3 EPSS 0.42%
-
HighCVSS 8.8 EPSS 0.38%
Tina is a headless content management system. Prior to version 2.2.2, @tinacms/graphql uses string-based path containment checks in FilesystemBridge. That blocks plain ../ traversal, but it does not resolve symlink or junction targets. If a symlink/junction already exists under t...
-
CVE-2026-33949 @tinacms/graphql has Path Traversal that leads to overwrite of arbitrary files
PublishedHighCVSS 8.1 EPSS 0.39%Tina is a headless content management system. Prior to version 2.2.2, a path traversal vulnerability in @tinacms/graphql allows unauthenticated users to write and overwrite arbitrary files within the project root. This is achieved by manipulating the relativePath parameter in Gra...
-
MediumCVSS 6.3 EPSS 0.50%
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 collecti...
-
HighCVSS 7.3 EPSS 0.48%
Tina is a headless content management system. In tinacms prior to version 3.1.1, tinacms uses the gray-matter package in an insecure way allowing attackers that can control the content of the processed markdown files, e.g., blog posts, to execute arbitrary code. tinacms version 3...
Sources: CVE.org, NVD, CISA KEV, FIRST EPSS, OSV and public exploit-reference metadata. Product matching comes from the published CVE records. A proof-of-concept means public code exists; it is not evidence of exploitation.