ChromeDevTools published a Moderate-severity security advisory on 22 October 2026 describing a workspace-boundary bypass in chrome-devtools-mcp. Advisory GHSA-5hw5-4q87-m6x9 lists versions 1.1.0 through 1.4.0 as affected and 1.5.0 as patched. The reported impact is overwriting files outside configured Model Context Protocol (MCP) roots, subject to the server’s filesystem permissions.[1]
The flaw concerns operation order. The server validates a caller-supplied output path, then enforces the output extension and writes to that changed path without validating the final destination. For example, workspace/report.txt can pass validation before becoming workspace/report.png. If the latter is a symbolic link to a writable file outside the root, the write follows it. Direct validation of that final link would reject it, according to the advisory.[1]
The source reports four reproductions, including a full MCP stdio workflow using the real server, Chrome and take_screenshot. It identifies screenshots as the demonstrated output and lists other paths sharing McpContext.saveFile. Exploitation requires an in-root symlink that an attacker or malicious workspace state can create or use; the advisory explicitly says this is not remote code execution and does not establish remote exploitation by itself.[1]
[1]: ChromeDevTools, “MCP roots bypass via extension-rewritten symlink output path,” 22 October 2026. https://github.com/ChromeDevTools/chrome-devtools-mcp/security/advisories/GHSA-5hw5-4q87-m6x9
Sources
Check or correct this page
Verification record
The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.
a3a8e72be35bee80c7c460a8a804af18d4d703bfc4ee2244df2547b7c7af2b12