Description
I originally reported this through Google Bug Hunters. The Google Bug Hunters team said this is in OSS VRP scope but not reward-eligible due to the project tier, and asked me to file an issue or PR directly with this repository. I am reporting it privately here first because it is an unfixed security issue.
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.
Recommendation
Update the chrome-devtools-mcp package to the latest compatible version. Followings are version details:
- Affected version(s): >= 0.24.0, <= 1.0.1
- Patched version(s): 1.1.0
References
Could your website be exposed too?
SmartScanner can check your website for chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots and gives you actionable findings to investigate.
Start a free scanRelated Issues
- Chrome DevTools for agents: daemon.pid write follows symlinks in /tmp fallback runtime directory - CVE-2026-53765
- Vue I18n: escapeParameter does not prevent XSS through srcdoc in translation messages - @intlify/core-base - CVE-2026-118257
- Svelte SSR does not validate dynamic element tag names in `<svelte:element>` - CVE-2026-27122
- Vue I18n: escapeParameter does not prevent XSS through srcdoc in translation messages - @intlify/core - CVE-2026-118257
