Workspace escape via unresolved symbolic links
Published Jun 24, 2026 · Updated Jun 24, 2026
Path traversal in Google Chrome DevTools MCP 0.24.0 through 1.0.1 allows local users to overwrite out-of-root files via symlinks. McpContext.validatePath() compares path.resolve() output with configured root strings without resolving links, after which file operations follow an accepted link outside the workspace. Exploitation requires an in-root symlink to an out-of-root target; upload_file can also read that target and send it to the selected page.
Summary
What happened
Path traversal in Google Chrome DevTools MCP 0.24.0 through 1.0.1 allows local users to overwrite out-of-root files via symlinks. McpContext.validatePath() compares path.resolve() output with configured root strings without resolving links, after which file operations follow an accepted link outside the workspace. Exploitation requires an in-root symlink to an out-of-root target; upload_file can also read that target and send it to the selected page.
The record
- CVE
- CVE-2026-53766
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- Go standard library
- Product
- Chrome DevTools MCP
- Classifications
- CWE-59, CWE-22, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.24.0, < 1.1.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Lab-only validatePath symlink write proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo