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.
References
| Link | Resource |
|---|---|
| https://github.com/ChromeDevTools/chrome-devtools-mcp/security/advisories/GHSA-3pvj-jv98-qhjq | Exploit Third Party Advisory |
Configurations
History
26 Jun 2026, 18:31
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:google:chrome-devtools-mcp:*:*:*:*:*:node.js:*:* | |
| First Time |
Google
Google chrome-devtools-mcp |
|
| References | () https://github.com/ChromeDevTools/chrome-devtools-mcp/security/advisories/GHSA-3pvj-jv98-qhjq - Exploit, Third Party Advisory |
24 Jun 2026, 22:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-06-24 22:16
Updated : 2026-06-26 19:16
NVD link : CVE-2026-53765
Mitre link : CVE-2026-53765
CVE.ORG link : CVE-2026-53765
JSON object : View
Products Affected
- chrome-devtools-mcp
CWE
CWE-59
Improper Link Resolution Before File Access ('Link Following')
