CVE-2026-106484 in chrome-devtools-mcp
Summary
by MITRE • 10/28/2026
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)
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 10/28/2026
The vulnerability identified as insufficient policy enforcement within the chrome-devtools-mcp component of Google Chrome for Linux versions prior to 1.5.0 represents a significant flaw in how the browser handles local resource access through its Model Context Protocol integration. This issue stems from an inadequate validation mechanism when processing file paths and content provided by local applications or scripts interacting with the developer tools interface. The core technical failure lies in the absence of strict boundary checks that would normally prevent the extension or protocol handler from accessing files outside of designated safe directories or bypassing standard permission models. By exploiting this gap, a malicious actor operating on the same local system can craft specific requests that trick the chrome-devtools-mcp into reading sensitive configuration files, user data, or other protected resources that should remain inaccessible to unprivileged processes.
From an operational perspective, this vulnerability allows for arbitrary read and write operations by any local attacker who has access to a standard user account on the affected Linux system. The ability to perform arbitrary reads means that confidential information such as browser history, saved passwords stored in local databases, or internal application configurations can be exfiltrated without requiring elevated privileges. Furthermore, the capability to execute arbitrary writes introduces the risk of data corruption or persistence mechanisms where an attacker could modify critical files used by Chrome or associated development tools. This effectively undermines the isolation principles that are central to modern browser security architectures, as it allows a lower-privilege process to influence higher-trust components through the MCP interface.
In terms of industry standard classifications, this vulnerability aligns closely with CWE-284 Improper Access Control and CWE-732 Incorrect Permission Assignment for Critical Resource. The failure to enforce proper policy boundaries is also indicative of weaknesses often associated with CWE-915 Improper Modification of Controls During Component Operation. From a threat modeling standpoint using the MITRE ATT&CK framework, this behavior maps to T1083 File and Directory Discovery, as it facilitates unauthorized enumeration of local file systems, and potentially T1222 File Permission Modification if write capabilities are leveraged for persistence or sabotage. The medium severity rating assigned by Chromium reflects that while exploitation requires local access, the impact on data confidentiality and integrity is substantial due to the sensitive nature of browser-stored information.
Mitigation strategies primarily involve upgrading the Google Chrome installation to version 1.5.0 or later where these policy enforcement mechanisms have been corrected. Until such an upgrade can be performed in a production environment, administrators should restrict local access to systems running vulnerable versions and disable any unnecessary MCP integrations that expose developer tools interfaces to untrusted local applications. Additionally, implementing strict file system permissions on directories containing sensitive Chrome data can provide a layer of defense-in-depth, ensuring that even if the application logic is bypassed, the underlying operating system prevents unauthorized reads or writes. Regular auditing of installed extensions and protocol handlers should also be conducted to minimize the attack surface available to local attackers seeking to exploit similar policy enforcement gaps in other components.