CVE-2026-33949: TinaCMS Path Traversal Vulnerability

CVE-2026-33949 Overview

CVE-2026-33949 is a path traversal vulnerability affecting TinaCMS, a headless content management system. The vulnerability exists in the @tinacms/graphql package prior to version 2.2.2, allowing unauthenticated users to write and overwrite arbitrary files within the project root by manipulating the relativePath parameter in GraphQL mutations.

Critical Impact

Attackers can replace critical server configuration files and potentially achieve arbitrary command execution by sabotaging build scripts.

Affected Products

• TinaCMS @tinacms/graphql package versions prior to 2.2.2

Discovery Timeline

• 2026-04-01 - CVE-2026-33949 published to NVD
• 2026-04-01 - Last updated in NVD database

Technical Details for CVE-2026-33949

Vulnerability Analysis

This path traversal vulnerability (CWE-22) allows attackers to escape the intended directory structure and access or modify files outside the designated content directories. The vulnerability stems from insufficient validation of the relativePath parameter within GraphQL mutations exposed by the @tinacms/graphql package.

When a user submits a GraphQL mutation to create or update content, the system fails to properly sanitize path traversal sequences (such as ../) in the relativePath parameter. This allows attackers to navigate the directory hierarchy and target files anywhere within the project root. The attack is particularly dangerous because it can be performed by unauthenticated users, requiring no authentication to exploit.

The primary impact is the ability to overwrite arbitrary files. This includes critical server configuration files such as package.json, build configuration files, or deployment scripts. By modifying these files, an attacker could inject malicious commands that would execute during the next build or deployment cycle, effectively achieving remote code execution.

Root Cause

The root cause is improper input validation in the @tinacms/graphql package. The relativePath parameter in GraphQL mutations is not adequately sanitized to prevent directory traversal sequences. The application fails to normalize the path or verify that the resolved path remains within the expected content directory boundaries before performing file write operations.

Attack Vector

The attack is network-based and requires no authentication or user interaction. An attacker can craft malicious GraphQL mutations containing path traversal sequences in the relativePath parameter. By including sequences like ../ in the path, the attacker can direct file writes to arbitrary locations within the project root.

For example, an attacker could target build scripts or configuration files to inject malicious code that executes during the application's build process. This could result in supply chain compromise, data exfiltration, or complete server takeover. The attack surface includes any TinaCMS deployment where the GraphQL endpoint is accessible, which is typical in headless CMS architectures.

The vulnerability mechanism involves submitting GraphQL mutations with manipulated relativePath values containing directory traversal sequences. Technical details and proof-of-concept information are available in the GitHub Security Advisory.

Detection Methods for CVE-2026-33949

Indicators of Compromise

• Unexpected modifications to configuration files such as package.json, build scripts, or deployment configurations
• GraphQL mutation requests containing path traversal sequences (../, ..%2f, or encoded variants) in the relativePath parameter
• Unusual file creation or modification activity within the project root directory
• Build process failures or unexpected behavior following file modifications

Detection Strategies

• Implement web application firewall (WAF) rules to detect and block path traversal patterns in request parameters
• Monitor GraphQL endpoint logs for mutations containing suspicious relativePath values with directory traversal sequences
• Configure file integrity monitoring (FIM) on critical configuration files and build scripts
• Analyze HTTP request logs for patterns indicating exploitation attempts against the TinaCMS GraphQL API

Monitoring Recommendations

• Enable detailed logging for all GraphQL mutations targeting content creation and update operations
• Set up alerts for file system changes in sensitive directories outside normal content paths
• Monitor for unexpected outbound connections or processes spawned during build cycles
• Implement real-time alerting for any detected path traversal attempts against the GraphQL endpoint

How to Mitigate CVE-2026-33949

Immediate Actions Required

• Upgrade @tinacms/graphql to version 2.2.2 or later immediately
• Audit file system for any unauthorized modifications, particularly to configuration files and build scripts
• Review GraphQL endpoint access controls and consider implementing authentication requirements
• Implement input validation at the network edge using a WAF to block path traversal attempts

Patch Information

TinaCMS has released version 2.2.2 which addresses this vulnerability. The patch implements proper sanitization of the relativePath parameter to prevent directory traversal attacks. Organizations should update their TinaCMS installation to version 2.2.2 or later. Refer to the GitHub Security Advisory for detailed patch information.

Workarounds

• Restrict network access to the GraphQL endpoint to trusted IP addresses only until the patch can be applied
• Implement a reverse proxy with strict path validation rules to filter malicious requests
• Deploy the TinaCMS instance in a containerized environment with read-only file system mounts for critical configuration files
• Use operating system-level file permissions to restrict write access to sensitive directories

# Example: Restrict GraphQL endpoint access via nginx
location /api/graphql {
    # Allow only trusted networks
    allow 10.0.0.0/8;
    allow 192.168.1.0/24;
    deny all;
    
    # Proxy to TinaCMS backend
    proxy_pass http://tinacms-backend:3000;
}