Vulnerability in chrome-devtools-mcp (CVE-2026-53765)
Summary
Vulnerability in chrome-devtools-mcp (CVE-2026-53765). Data can be tampered with by attackers. Exploitable via O_NOFOLLOW. 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.20.0 until 1.1.0, The chrome-devtools-mcp daemon writes its PID file with fs.writeFileSync() to a deterministic runtime path. On typical macOS environments, and on Linux sessions where $XDG_RUNTIME_DIR is unset, that runtime path falls back to /tmp/chrome-devtools-mcp-/daemon.pid. Because the write does not use O_NOFOLLOW, a local low-privilege user on the same POSIX host can pre-create /tmp/chrome-devtools-mcp-/daemon.pid as a symlink to a file writable by the victim. When the victim later starts daemon mode, fs.writeFileSync() follows the symlink and truncates the target file to the daemon PID string. This vulnerability is fixed in 1.1.0.
Source: GitHub Security Advisories (Global) 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-53765 has been found in chrome-devtools-mcp.
Attackers can target a specific entry point like O_NOFOLLOW 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-53765" on the vendor's site.
CVE-2026-53765 (chrome-devtools-mcp) — CWE-59 / CVSS v3 6.1
Attack vector: local / no user interaction
Attack surface: O_NOFOLLOW / daemon.pid / pidfile_symlink_poc.cjs
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.
A vulnerability (CWE-59) exists in chrome-devtools-mcp. Attackers reach the vulnerable code path via O_NOFOLLOW.
Check the vendor advisory for the affected versions of chrome-devtools-mcp. Attack surface: O_NOFOLLOW / daemon.pid / pidfile_symlink_poc.cjs.
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