CVE-2026-53765: Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome brow

Q: How do I fix CVE-2026-53765?

chrome-devtools-mcp: upgrade to 1.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-53765 being exploited?

CVE-2026-53765 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-53765 affect?

CVE-2026-53765 affects chrome-devtools-mcp. Severity is medium (CVSS 6.1). 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 runtim

Q: How urgent is CVE-2026-53765?

Priority 27/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2026-53765 is a medium-severity flaw (CVSS 6.1) affecting chrome-devtools-mcp. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.1 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.1% (top 99%)
CISA exploited list	No
Weakness	CWE-59
Published	2026-06-24
Last modified	2026-10-25

Publisher (CNA): GitHub, Inc. · Vendor: google

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-24 22:16 UTCPublished CVE record published
2026-10-25 23:10 UTCUpdated Record last modified

google chrome-devtools-mcp UPGRADE

Affected: >= 0.20.0 and < 1.1.0

Fixed in: 1.1.0

Safe to downgrade to: a release before 0.20.0

1. Check installed version

npm ls chrome-devtools-mcp

2. UPGRADE to 1.1.0

npm install chrome-devtools-mcp@">=1.1.0"

3. If no update is available yet, DOWNGRADE to a release before 0.20.0

npm view chrome-devtools-mcp versions npm install chrome-devtools-mcp@"<0.20.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-53765?

chrome-devtools-mcp: upgrade to 1.1.0. Exact commands for each OS are on this page.

Is CVE-2026-53765 being exploited?

CVE-2026-53765 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-53765 affect?

CVE-2026-53765 affects chrome-devtools-mcp. Severity is medium (CVSS 6.1). 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 runtim

How urgent is CVE-2026-53765?

Priority 27/100. Public exploit reference

Software pages

macOS vulnerabilities · Google Chrome vulnerabilities

Related CVEs

CVE-2026-53766 MEDIUM 6.1 UPGRADE Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome brow

References

← Back to latest CVEs