CVE-2026-53766: 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-53766?

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

Q: Is CVE-2026-53766 being exploited?

CVE-2026-53766 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-53766 affect?

CVE-2026-53766 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.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textua

Q: How urgent is CVE-2026-53766?

Priority 27/100. Public exploit reference

Routine

MEDIUM 6.1UPGRADE

CVE-2026-53766 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.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textually falls under one of the configured root paths. path.resolve() does not canonicalize symbolic links. As a result, a symlink inside a configured workspace root can point to a file outside that root, pass valid

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 98%)
CISA exploited list	No
Weakness	CWE-22, 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.24.0 and < 1.1.0

Fixed in: 1.1.0

Safe to downgrade to: a release before 0.24.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.24.0

npm view chrome-devtools-mcp versions npm install chrome-devtools-mcp@"<0.24.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-53766?

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

Is CVE-2026-53766 being exploited?

CVE-2026-53766 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-53766 affect?

CVE-2026-53766 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.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textua

How urgent is CVE-2026-53766?

Priority 27/100. Public exploit reference

Software pages

Google Chrome vulnerabilities

Related CVEs

CVE-2026-53765 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