Vulnerability in Chromedevtools Chrome-Devtools-Mcp

CVE-2026-53765

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 6.1 (Medium). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L.

EPSS exploit prediction

EPSS: 0.001 (0.9th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 1st percentile — 0.9% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2026-53765: held from 0.001 to 0.001.

EPSS over last 30 days · oldest: 0.001 · newest: 0.001 · change: 0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2026-53765?
CVE-2026-53765 is a medium-severity vulnerability in Chromedevtools Chrome-Devtools-Mcp, classified under Improper Link Resolution Before File Access. CVSS score: 6.1/10. Published 2026-06-24.
How severe is CVE-2026-53765?
Medium severity. CVSS v3 base score is 6.1 out of 10.