boxscore/security
CVE · referencelatest edition

Reference page — cumulative record through Wednesday, August 19, 2026 UTC. Reference pages update as the archive grows; only dated daily editions are immutable pages of record.

CVE-2026-53766MEDIUM
ChromeDevTools chrome-devtools-mcp — chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots
  AV  AC  PR  UI  S  C  I  A   CVSS    EPSS   %ile   KEV
   L   L   L   N  U  N  H  L    6.1   .0011    1.3     —
AFFECTED
  Product              Versions              Fixed
  chrome-devtools-mcp  >= 0.24.0, < 1.1.0 –  —
TIMELINE
  Jun 10  Reserved by GitHub_M
  Jun 24  EXPLOIT PUBLISHED — CVE-2026-53766 (ChromeDevTools chrome-devtools-mcp). Public exploit reference added.
  Jun 24  Published (CNA: GitHub_M)
CWE-22, CWE-59 · CNA: GitHub_M · CVSS v3.1 · 1 reference · NVD status: Analyzed

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.

Lifecycle

Complete event history — 3 events, chronological
DateEventDetail
June 10, 2026ReservedReserved by GitHub_M
June 24, 2026EXPLOIT PUBLISHEDEXPLOIT PUBLISHED — CVE-2026-53766 (ChromeDevTools chrome-devtools-mcp). Public exploit reference added.
June 24, 2026PublishedPublished (CNA: GitHub_M)

Affected

Affected products and packages — 1 row
VendorProduct / PackageEcosystemVersion introducedFixed
ChromeDevToolschrome-devtools-mcp>= 0.24.0, < 1.1.0

Weaknesses

CWE-22 · CWE-59

References (1)

Related

Authoritative record: CVE-2026-53766 at cve.org

Vendors: chromedevtools

Weaknesses: CWE-22 · CWE-59

About this page

This is a reference page, not a dated page of record. It assembles the complete lifecycle of CVE-2026-53766 from the CVE Program record, NVD enrichment, the CISA KEV catalog, EPSS, and OSV advisories. The box score's numbers (CVSS, EPSS, KEV status) are current as of Wednesday, August 19, 2026 UTC and are re-derived as the archive grows; only dated daily editions are immutable pages of record. The authoritative source for this identifier is cve.org.