Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-53766 medium CVSS 6.1

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.

AI summary snake-internal / snake-material-v2

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.
❓ What is the problem
**Path traversal** (CWE-22) exists in chrome-devtools-mcp. Attackers reach the vulnerable code path via ``roots`` without authentication.
📍 Affected scope
chrome-devtools-mcp — . Attack surface: `roots` / `upload_file` / `O_NOFOLLOW` / `filePath`.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Data can be tampered with by attackers
🔧 How to fix
Update to **1.1.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
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 (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'chrome-devtools-mcp' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `chrome-devtools-mcp` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade chrome-devtools-mcp to 1.1.0

    ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

npm chrome-devtools-mcp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.1.0"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →