CVE-2026-53766

MEDIUM
MEDIUM Priority: 0.01 BB Relevance: 37/100
Published: 2026-06-24 Modified: 2026-10-25 First seen: 2026-10-29 Status: active

Attack Surface

Low Complexity No Interaction Integ. Impact

CVSS Vector Breakdown

AV: Local
AC: Low
PR: Low
UI: None
S: Unchanged
C: None
I: High
A: Low

Description

Chrome DevTools for agents (chrome-devtools-mcp) lets your coding agent control and inspect a live Chrome browser. From 0.24.0 until 1.1.0, McpContext.validatePath() enforces workspace roots by checking whether path.resolve(filePath) textually falls under one of the configured root paths. path.resolve() does not canonicalize symbolic links. As a result, a symlink inside a configured workspace root can point to a file outside that root, pass validation, and then be followed by downstream file read/write operations. This bypass applies even when the MCP client correctly declares the roots capability with a non-empty list. It is separate from the documented legacy behavior where missing roots capability allows all paths. The practical impact is a workspace-boundary bypass. In the write direction, filePath-writing tools can overwrite out-of-root files through an in-root symlink. In the read direction, upload_file can read through the symlink and send the file to the currently selected web page. This vulnerability is fixed in 1.1.0.

Weakness Classification (2)

Affected Software (1)

VendorProductVersion
google chrome-devtools-mcp 0.24.0 – 1.1.0

Bug Bounty Relevance

37 / 100
✓ Low complexity
✓ No user interaction

CVSS Score

6.1 / 10.0 v3.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

EPSS — Exploitation Probability

0.12%
Raw Score 0.001170
Percentile 1.7%
Date 2026-10-29

EPSS Trend

2026-10-29
0.00117
2026-10-28
0.00117

Intelligence Sources

nvd ref →