Quick answers
- Is CVE-2026-33949 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-33949 being exploited in the wild.
- How severe is CVE-2026-33949?
- Low severity, with a CVSS score of 3.1, published 30 March 2026.
- Which products and versions are affected?
- @tinacms/graphql (npm) SEMVER:introduced=0,fixed=2.2.2.
- Is there a fix for CVE-2026-33949?
- Yes. @tinacms/graphql (npm): upgrade to 2.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-33949 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-33949?
- Check whether you run @tinacms/graphql (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @tinacms/graphql (npm): upgrade to 2.2.2 or later
npm install @tinacms/graphql@2.2.2
Technical details
A path traversal vulnerability exists in @tinacms/graphql's path validation logic (getValidatedPath function in resolver/index.ts). The regex-based validation fails to recognize backslashes (\) as directory separators on non-Windows platforms (Linux/macOS), allowing attackers to bypass the check using payloads like "x\..\..\..\package.json" in the relativePath parameter of GraphQL mutations. The validation flaw, combined with platform-specific path normalization in fs modules, permits unauthenticated attackers with network access to the GraphQL API to write and overwrite arbitrary files within the project root. Patches are available in version 2.2.2 and later.
Affected products
- TinaCMS @tinacms/graphql <= 2.2.1
Identifiers
- CVE-2026-33949
- GHSA-v9p7-gf3q-h779
Timeline
- 2026-03-30: disclosed
- 2026-03-30: patched: Fixed in version 2.2.2