What happened
Insufficient policy enforcement in chrome-devtools-mcp before 1.5.0 lets a local attacker achieve arbitrary read/write via a malicious file. No CVSS score is assigned; it carries Chromium's Medium severity and is only reachable by a local actor.
Why it matters
chrome-devtools-mcp is an MCP tool surface for browser-driving agents; a local attacker can obtain arbitrary file read/write on the developer's host from the agent's browser-control channel, which can be used to harvest credentials or tamper with agent state.
Attack vector
A local attacker uses a malicious file to trigger insufficient policy enforcement in chrome-devtools-mcp, performing arbitrary file read/write on the machine running the MCP server.
Affected systems
chrome-devtools-mcp >= 1.1.0, < 1.5.0 (Google Chrome on Linux)
Mitigation
Upgrade to chrome-devtools-mcp 1.5.0 (GHSA-5hw5-4q87-m6x9).