CVE-2026-106484: Google chrome-devtools-mcp · Insufficient Policy Enforcement
Affects Google chrome-devtools-mcpSource CVE Database V5
Not known to be exploited : upgrade to 1.5.0 when convenient.
Data as of 28 Oct 2026, 18:44 UTC
Rated Medium by the CNA (Chrome) · CVSS not yet scored by NVD
- Patch
- Available – fixed in 1.5.0
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Upgrade chrome-devtools-mcp and chromedevtools/chrome-devtools-mcp to 1.5.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Googlechrome-devtools-mcp | Affected
| Fixed in
|
GitHubchromedevtools/chrome-devtools-mcppkg:github/chromedevtools/chrome-devtools-mcpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade chrome-devtools-mcp to version 1.5.0 or later, where this vulnerability has been fixed.
Description
A vulnerability in Google Chrome's chrome-devtools-mcp component on Linux prior to version 1.5.0 allows a local attacker to perform arbitrary read and write operations via a malicious file due to insufficient policy enforcement. This issue has been fixed in version 1.5.0.