Vulnerability Description
Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.20.0 until 1.1.0, The chrome-devtools-mcp daemon writes its PID file with fs.writeFileSync() to a deterministic runtime path. On typical macOS environments, and on Linux sessions where $XDG_RUNTIME_DIR is unset, that runtime path falls back to /tmp/chrome-devtools-mcp-<uid>/daemon.pid. Because the write does not use O_NOFOLLOW, a local low-privilege user on the same POSIX host can pre-create /tmp/chrome-devtools-mcp-<victim_uid>/daemon.pid as a symlink to a file writable by the victim. When the victim later starts daemon mode, fs.writeFileSync() follows the symlink and truncates the target file to the daemon PID string. This vulnerability is fixed in 1.1.0.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Chrome-Devtools-Mcp | >= 0.20.0, < 1.1.0 |
Related Weaknesses (CWE)
References
- https://github.com/ChromeDevTools/chrome-devtools-mcp/security/advisories/GHSA-3ExploitThird Party Advisory
FAQ
What is CVE-2026-53765?
CVE-2026-53765 is a vulnerability with a CVSS score of 6.1 (MEDIUM). Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.20.0 until 1.1.0, The chrome-devtools-mcp daemon writes its PID file with fs.w...
How severe is CVE-2026-53765?
CVE-2026-53765 has been rated MEDIUM with a CVSS base score of 6.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-53765?
Check the references section above for vendor advisories and patch information. Affected products include: Google Chrome-Devtools-Mcp.