Skip to content

CVE-2026-53765 chrome-devtools-mcp: daemon.pid write follows symlinks in /tmp fallback runtime directory

MediumCVSS 6.1 EPSS 0.10%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

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.

Upgrade path

3 packages: 2 fixed.

PackageAffectedFixed inStatus
Google chrome-devtools-mcp >= 0.20.0, < 1.1.0 1.1.0 Fixed
npm chrome-devtools-mcp(npm) >= 0.20.0, < 1.1.0; >= 0.20.0, <= 1.0.1 1.1.0 Fixed
ChromeDevTools chrome-devtools-mcp = >= 0.20.0, < 1.1.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
ChromeDevTools chrome-devtools-mcp = >= 0.20.0, < 1.1.0 No fix listed
npm chrome-devtools-mcp(npm) >= 0.20.0, <= 1.0.1 No fix listed
Google chrome-devtools-mcp >= 0.20.0, < 1.1.0 1.1.0
npm chrome-devtools-mcp(npm) >= 0.20.0, < 1.1.0 1.1.0

References