7.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2026-34604

CVE-2026-34604: @tinacms/graphql's `FilesystemBridge` Path Validation Can Be Bypassed via Symlinks or Junctions

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 the allowed content root, a path like content/posts/pivot/owned.md is still considered "inside" the base even though the real filesystem target can be outside it. As a result, FilesystemBridge.get(), put(), delete(), and glob() can operate on files outside the intended root. This issue has been patched in version 2.2.2.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2026-34604

CVE-2026-34604:

7.1

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
@tinacms/graphql	npm	<= 2.2.0	2.2.2

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability exists in the @tinacms/graphql package and is a classic path traversal issue (CWE-22) combined with improper link resolution (CWE-59). The root cause is the assertWithinBase function in packages/@tinacms/graphql/src/database/bridge/filesystem.ts, which was responsible for ensuring that file operations occurred within a designated base directory. This function's validation was purely lexical; it used path.resolve and string comparisons (startsWith) to check for path containment. It failed to account for symlinks or Windows junctions.

An attacker could create a symlink inside the allowed content directory that points to an arbitrary location on the filesystem. When a GraphQL operation (like read, write, or delete) was performed on a path that traversed this symlink, the assertWithinBase check would pass because the lexical path appeared to be within the allowed directory. However, the underlying filesystem operation would follow the symlink, resulting in access to files or directories outside the intended root.

The FilesystemBridge class methods get, put, delete, and glob all relied on this flawed assertWithinBase function for security validation, making them the direct vectors for exploitation. The patch addresses this by modifying assertWithinBase to use fs.realpathSync to resolve the canonical filesystem path of both the target and the base directory, ensuring that the final path is truly contained within the base directory before allowing any I/O operations.

Vulnerable functions

assertWithinBase

packages/@tinacms/graphql/src/database/bridge/filesystem.ts

This function was vulnerable because it only performed a lexical path validation using `path.resolve` and `startsWith`. It did not resolve symlinks, which could be used to bypass the directory containment check. An attacker could create a symlink within the allowed directory that points to a location outside of it, and this validation would still pass, leading to arbitrary file access.

FilesystemBridge.get

packages/@tinacms/graphql/src/database/bridge/filesystem.ts

The `get` method uses the vulnerable `assertWithinBase` function to validate the `filepath` parameter before reading a file from the filesystem. Because `assertWithinBase` could be bypassed using symlinks, an attacker could use this method to read arbitrary files from the filesystem.

FilesystemBridge.put

packages/@tinacms/graphql/src/database/bridge/filesystem.ts

The `put` method uses the vulnerable `assertWithinBase` function to validate the `filepath` parameter before writing a file to the filesystem. This allowed an attacker to write arbitrary files to any location on the filesystem by crafting a path that includes a symlink.

FilesystemBridge.delete

packages/@tinacms/graphql/src/database/bridge/filesystem.ts

The `delete` method uses the vulnerable `assertWithinBase` function to validate the `filepath` parameter before deleting a file. This vulnerability could be exploited by an attacker to delete arbitrary files on the filesystem by using a symlink to bypass the path validation.

FilesystemBridge.glob

packages/@tinacms/graphql/src/database/bridge/filesystem.ts

The `glob` method is also affected by the path traversal vulnerability. Although not explicitly shown in the code snippets of the advisory, the description confirms that it uses the same flawed validation logic, allowing an attacker to list files in directories outside of the intended root by using a symlink.

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.