Dashboard / CVE-2026-53765

CVE-2026-53765

MEDIUM
MEDIUM Priority: 0.01 BB Relevance: 37/100
Published: 2026-06-24 Modified: 2026-10-25 First seen: 2026-10-29 Status: active

Attack Surface

Low Complexity No Interaction Integ. Impact

CVSS Vector Breakdown

AV: Local
AC: Low
PR: Low
UI: None
S: Unchanged
C: None
I: High
A: Low

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.

Weakness Classification (1)

Affected Software (1)

VendorProductVersion
google chrome-devtools-mcp 0.20.0 – 1.1.0

References & Advisories (1)

Bug Bounty Relevance

37 / 100
✓ Low complexity
✓ No user interaction

CVSS Score

6.1 / 10.0 v3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

EPSS — Exploitation Probability

0.10%
Raw Score 0.001040
Percentile 1.0%
Date 2026-10-29

EPSS Trend

2026-10-29
0.00104
2026-10-28
0.00104

Intelligence Sources

nvd ref →

External Links