chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots
CVE-2026-53766 · GHSA-8qf9-62x2-82pp · published 2026-08-17
- Severity
- Medium
- CVSS score
- 6.1
- Chance of exploitation (EPSS)
- 0.12%
- Fixed in
- 1.1.0
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Who can exploit: A local process/user or trusted workflow that can create a symlink inside the workspace. A remote page/prompt-injection attacker, if a suitable workspace-internal symlink already exists or can be created by another trusted workflow/tool. Security impact: Integrity: tools that write to filePath can overwrite files outside the configured workspace root through an in-root symlink. Confidentiality: upload_file can read a file outside the workspace through an in-root symlink and attach it to a file input on the current page.
Upgrade chrome-devtools-mcp to 1.1.0 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| chrome-devtools-mcp | npm | >= 0.24.0, <= 1.0.1 | 1.1.0 |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
- MediumChrome DevTools for agents: daemon.pid write follows symlinks in /tmp fallback runtime directorychrome-devtools-mcp
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.