Vulnerability · Published Jun 24, 2026 · Assigned by GitHub_M
CVE-2026-53766chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots
Medium 6.1
In plain English
A medium-severity path traversal in chrome-devtools-mcp from ChromeDevTools. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 2% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official 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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| npm | chrome-devtools-mcp | 1.1.0 | GHSA-8qf9-62x2-82pp |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| ChromeDevTools | chrome-devtools-mcp | >= 0.24.0, < 1.1.0 |
Weakness: CWE-22, CWE-59 · Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L