Path Traversal in chrome-devtools-mcp (CVE-2026-53766)
Summary
Path traversal in chrome-devtools-mcp (CVE-2026-53766). Data can be tampered with by attackers. Exploitable via roots. Mitigation: upgrade to 1.1.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-53766 has been found in chrome-devtools-mcp.
Attackers can target a specific entry point like roots over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.1/10.
What to do: upgrade chrome-devtools-mcp to 1.1.0 or later.
If unsure, ask your IT team or search "chrome-devtools-mcp CVE-2026-53766" on the vendor's site.
CVE-2026-53766 (chrome-devtools-mcp) — CWE-22 / CVSS v3 6.1
Attack vector: local / no user interaction
Attack surface: roots / upload_file / O_NOFOLLOW / filePath
Patched: 1.1.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in chrome-devtools-mcp. Attackers reach the vulnerable code path via roots.
Check the vendor advisory for the affected versions of chrome-devtools-mcp. Attack surface: roots / upload_file / O_NOFOLLOW / filePath.
Severity: Medium (CVSS 6.1/10). Data can be tampered with by attackers.
Update to 1.1.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'chrome-devtools-mcp' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'chrome-devtools-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
chrome-devtools-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade chrome-devtools-mcp to 1.1.0ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com