Skip to content

CVE-2026-53766 chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots

MediumCVSS 6.1 EPSS 0.12%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
Proof of concept public · automatable: no · technical impact: partial

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.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
Google chrome-devtools-mcp >= 0.24.0, < 1.1.0 1.1.0 Fixed
npm chrome-devtools-mcp(npm) >= 0.24.0, < 1.1.0; >= 0.24.0, <= 1.0.1 1.1.0 Fixed
ChromeDevTools chrome-devtools-mcp = >= 0.24.0, < 1.1.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
ChromeDevTools chrome-devtools-mcp = >= 0.24.0, < 1.1.0 No fix listed
npm chrome-devtools-mcp(npm) >= 0.24.0, <= 1.0.1 No fix listed
Google chrome-devtools-mcp >= 0.24.0, < 1.1.0 1.1.0
npm chrome-devtools-mcp(npm) >= 0.24.0, < 1.1.0 1.1.0

References