---
id: "CVE-2026-106484"
kind: "vulnerability"
aliases: ["CVE-2026-106484"]
title: "chrome-devtools-mcp: policy flaw lets local attacker read and write files"
severity: "medium"
cvss: null
epss: null
exploited: false
status: "open"
category: "ai-tooling"
products: []
ecosystems: []
tags: ["ai-tooling", "chrome-devtools-mcp", "claude-code", "linux", "local-dev", "mcp"]
not_affected_if: ["mcp-not-installed", "not-linux", "version-1.5.0-or-later"]
published_at: "2026-10-28T19:17:21+00:00"
first_seen_at: "2026-10-28T19:34:54+00:00"
updated_at: "2026-10-28T19:36:17+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-106484", "first_seen_at": "2026-10-28T19:34:54+00:00"}]
---

# chrome-devtools-mcp: policy flaw lets local attacker read and write files

The chrome-devtools-mcp server bundled with Google Chrome on Linux fails to enforce its policy when handling a malicious file. A local attacker can use it to perform arbitrary reads and writes.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed chrome-devtools-mcp version, for example with `npx chrome-devtools-mcp --version` or by reviewing the package.json of the project that depends on it
- unknown for other checks, as the sources do not say how to detect it in a deployment

## Fix

- Upgrade chrome-devtools-mcp to `1.5.0` or later
- unknown for Google Chrome versions, as the sources do not name a fixed Chrome build

## Timeline

- 2026-10-28T19:34:54+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-106484

## From the sources

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)

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_