CVE-2026-106484 Insufficient policy enforcement in chrome-devtools-mcp in Google Chrome on Linux prior to 1.5.0 allowed a local attacker to perform arbitrar
Medium 4.4
Published
Updated
Check this codebase for CVE-2026-106484 and fix it if it is affected.
What it is: CVE-2026-106484 is a medium-severity vulnerability in Google chrome-devtools-mcp, published on 28 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-106484 in the wild and no public exploit code.
Affected product: Google chrome-devtools-mcp. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-106484/ (Markdown: https://insights.sbomify.com/CVE-2026-106484/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-106484?
CVE-2026-106484 is a medium-severity vulnerability in Google chrome-devtools-mcp, published on 28 Oct 2026.
Official description
Insufficient policy enforcement in chrome-devtools-mcp in Google Chrome on Linux prior to 1.5.0 allowed a local attacker to perform arbitrary read/write via a malicious file. (Chromium security severity: Medium)
Weakness: CWE-284
Which versions are affected by CVE-2026-106484?
How do I fix CVE-2026-106484?
No fix has been published for CVE-2026-106484 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-106484 being exploited?
There is no known exploitation of CVE-2026-106484 in the wild and no public exploit code.
Sources
Also known as GHSA-2mw5-2f2c-v2g3, GHSA-5hw5-4q87-m6x9.