Skip to main content
VulnerabilityPublished Updated

CVE-2026-53765: ChromeDevTools chrome-devtools-mcp · Link Following

Affects ChromeDevTools chrome-devtools-mcpSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.1 Medium : upgrade to 1.1.0 when convenient.

Data as of 6 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.1Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.1.0
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Upgrade chrome-devtools-mcp and chromedevtools/chrome-devtools-mcp to 1.1.0.

Affected software

ProductAffectedFixed in
ChromeDevToolschrome-devtools-mcpAffected
  • >=0.20.0 <1.1.0
Fixed in
  • 1.1.0
GitHubchromedevtools/chrome-devtools-mcppkg:github/chromedevtools/chrome-devtools-mcpOther threatsAffected
  • >=0.20.0 <1.1.0
Fixed in
  • 1.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in chrome-devtools-mcp version 1.1.0. Users should upgrade to version 1.1.0 or later to remediate this vulnerability. Until upgrading, avoid running the daemon in environments where untrusted local users have write access to /tmp or the runtime directory. Patch status is not explicitly stated in vendor advisory content but the description confirms the issue is fixed in 1.1.0.

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.

References

Community reviews

Loading reviews…