CVE-2026-33949
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedTina 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 GraphQL mutations. The impact includes the ability to replace critical server configuration files and potentially execute arbitrary commands by sabotaging build script. This issue has been patched in version 2.2.2.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in @tinacms/graphql allows unauthenticated attackers to write or overwrite arbitrary files within the project root by manipulating the relativePath parameter in GraphQL mutations. This enables replacement of critical server configuration files and potentially RCE via sabotage of build scripts.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 2.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify @tinacms/graphql installationRun 'npm list @tinacms/graphql' or check package.json dependencies to determine the installed version of @tinacms/graphqlAffected if The installed version is 2.2.1 or lower
-
Locate GraphQL endpoint configurationSearch project source code for GraphQL endpoint definitions, typically in files like graphql.ts, api.ts, or server configuration files. Look for routes registering @tinacms/graphql handlersAffected if A GraphQL endpoint is exposed without authentication middleware
-
Inspect relativePath parameter handlingExamine the source code of GraphQL mutation handlers in @tinacms/graphql, specifically functions that process the relativePath parameter in file operationsAffected if The relativePath parameter is used directly in file path operations without validation or path sanitization
-
Check for authentication on GraphQL APIReview the server configuration or middleware stack that handles GraphQL requests. Determine if authentication is required before mutation executionAffected if GraphQL mutations can be executed without authentication credentials
You are affected if @tinacms/graphql version 2.2.1 or lower is installed AND your GraphQL endpoint is accessible without authentication, allowing the relativePath parameter to be manipulated for arbitrary file writes.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade TinaCMS to version 2.2.2 or later to apply the patch.
@tinacms/graphql version 2.2.2 or later
- Check the current version of @tinacms/graphql in your project dependencies (package.json or package-lock.json)
- Run 'npm update @tinacms/graphql' or 'npm install @tinacms/[email protected]' to upgrade to the fixed version
- Run 'npm install' to ensure all dependencies are properly resolved
- Verify the upgrade was successful by checking the installed version with 'npm list @tinacms/graphql'
- Test your application to ensure the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data