Back to overview

CVE-2026-53765

MEDIUM
6.1
CVSS 3.1
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.

Metadata

CVE ID
CVE-2026-53765
State
PUBLISHED
Assigner
GitHub_M
Reserved
2026-06-10 17:48 UTC
Published
2026-06-24 21:30 UTC
Last updated
2026-06-24 21:30 UTC
Primary CWE
CWE-59
CWE-59: Improper Link Resolution Before File Access ('Link F…
Vendor / Product
ChromeDevTools / chrome-devtools-mcp
Sources
cve.org  ·  NVD

Severity & Metrics

6.1 MEDIUM CVSS 3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
Affected products (1)
VendorProductPlatformVersions
ChromeDevTools chrome-devtools-mcp — >= 0.20.0, < 1.1.0
Weakness (CWE)
CWESourceDescription
CWE-59 cna CWE-59: Improper Link Resolution Before File Access ('Link Following')
CVSS scores (1)
ScoreSeverityVersionSourceVector
6.1 MEDIUM 3.1 cna CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
References (1)
Back to overview