CVE-2026-53766: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in ChromeDevTools chrome-devtools-mcp
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textually falls under one of the configured root paths. path.resolve() does not canonicalize symbolic links. As a result, a symlink inside a configured workspace root can point to a file outside that root, pass validation, and then be followed by downstream file read/write operations. This bypass applies even when the MCP client correctly declares the roots capability with a non-empty list. It is separate from the documented legacy behavior where missing roots capability allows all paths. The practical impact is a workspace-boundary bypass. In the write direction, filePath-writing tools can overwrite out-of-root files through an in-root symlink. In the read direction, upload_file can read through the symlink and send the file to the currently selected web page. This vulnerability is fixed in 1.1.0.
AI Analysis
Technical Summary
The vulnerability in chrome-devtools-mcp (CVE-2026-53766) involves improper limitation of a pathname to a restricted directory (CWE-22) due to the use of path.resolve() which does not canonicalize symbolic links. The McpContext.validatePath() method checks if a file path falls under configured workspace roots by textual comparison, but symlinks inside the root can point outside, bypassing this check. This allows an attacker to read files outside the workspace via upload_file or overwrite files outside the workspace through symlinked paths. The vulnerability affects versions >=0.24.0 and <1.1.0 and is fixed in 1.1.0.
Potential Impact
The vulnerability allows an attacker with local privileges to bypass workspace boundaries and perform unauthorized file read and write operations outside the configured workspace roots. This can lead to integrity violations by overwriting files and potential information disclosure by reading arbitrary files. The CVSS score is 6.1 (medium severity) with low attack vector (local), low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and low availability impact.
Mitigation Recommendations
Upgrade chrome-devtools-mcp to version 1.1.0 or later, where this path traversal vulnerability is fixed. No other mitigations are documented. Patch status is not explicitly stated in vendor advisories but the fix is confirmed in version 1.1.0.
CVE-2026-53766: CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in ChromeDevTools chrome-devtools-mcp
Description
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textually falls under one of the configured root paths. path.resolve() does not canonicalize symbolic links. As a result, a symlink inside a configured workspace root can point to a file outside that root, pass validation, and then be followed by downstream file read/write operations. This bypass applies even when the MCP client correctly declares the roots capability with a non-empty list. It is separate from the documented legacy behavior where missing roots capability allows all paths. The practical impact is a workspace-boundary bypass. In the write direction, filePath-writing tools can overwrite out-of-root files through an in-root symlink. In the read direction, upload_file can read through the symlink and send the file to the currently selected web page. This vulnerability is fixed in 1.1.0.
CVSS v3.1
Score 6.1medium
Affected software
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in chrome-devtools-mcp (CVE-2026-53766) involves improper limitation of a pathname to a restricted directory (CWE-22) due to the use of path.resolve() which does not canonicalize symbolic links. The McpContext.validatePath() method checks if a file path falls under configured workspace roots by textual comparison, but symlinks inside the root can point outside, bypassing this check. This allows an attacker to read files outside the workspace via upload_file or overwrite files outside the workspace through symlinked paths. The vulnerability affects versions >=0.24.0 and <1.1.0 and is fixed in 1.1.0.
Potential Impact
The vulnerability allows an attacker with local privileges to bypass workspace boundaries and perform unauthorized file read and write operations outside the configured workspace roots. This can lead to integrity violations by overwriting files and potential information disclosure by reading arbitrary files. The CVSS score is 6.1 (medium severity) with low attack vector (local), low attack complexity, low privileges required, no user interaction, unchanged scope, no confidentiality impact, high integrity impact, and low availability impact.
Mitigation Recommendations
Upgrade chrome-devtools-mcp to version 1.1.0 or later, where this path traversal vulnerability is fixed. No other mitigations are documented. Patch status is not explicitly stated in vendor advisories but the fix is confirmed in version 1.1.0.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-10T17:48:40.547Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3c501d4853345fc1e45bcb
Added to database: 06/24/2026, 21:46:05 UTC
Last enriched: 07/01/2026, 22:36:16 UTC
Last updated: 08/08/2026, 12:41:11 UTC
Views: 81
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.