p PatchFirst

CVE-2026-53766

CVE-2026-53766 · chrome-devtools-mcp: validatePath() does not canonicalize symlinks before enforcing roots

Cette page présente des faits issus de sources publiques. Consultez l’avis original avant toute mise à jour.

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.

CVSS 6.1 · Moyenne · EPSS 0,1% · Correctif disponible

Publication
Mise à jour

Pile logicielle: node

Produits et versions concernés

  • chrome-devtools-mcp

    Versions du logiciel
    • >= 0.24.0, < 1.1.0: Concernée

    Aucun correctif publié

  • chrome-devtools-mcp npm

    Plages de versions concernées
    • SEMVER: ≥ 0.24.0, < 1.1.0

    Mettez à jour vers 1.1.0

Sources originales

Vérifiez votre serveur →