CVE-2026-53765

MEDIUMPre-NVD 6.16.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 100% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
6.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.1
EG Score
6.1(medium)
EPSS
0.2%
KEV
Not listed

Published

June 17, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

daemon.pid write follows symlinks in /tmp fallback runtime directory · Advisory · ChromeDevTools/chrome-devtools-mcp · GitHub

https://github.com/ChromeDevTools/chrome-devtools-mcp/security/advisories/GHSA-3pvj-jv98-qhjq

Vendor Advisories for CVE-2026-53765(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
chrome-devtools-mcp—1.1.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 12× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 08:41 UTCEG score recompute
  2. 2026-07-06 06:35 UTCEG score recompute
  3. 2026-07-05 04:35 UTCEG score recompute
  4. 2026-07-05 02:31 UTCEPSS rescore
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-04 01:43 UTCEG score recompute
  9. 2026-07-02 23:37 UTCEG score recompute
  10. 2026-07-01 21:37 UTCEG score recompute
  11. 2026-07-01 15:07 UTCEPSS rescore
  12. 2026-06-30 19:37 UTCEG score recompute
  13. 2026-06-29 17:36 UTCEG score recompute
  14. 2026-06-28 15:34 UTCEG score recompute
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 13:34 UTCEG score recompute
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-26 11:33 UTCEG score recompute
  20. 2026-06-25 13:49 UTCEPSS rescore
  21. 2026-06-25 04:18 UTCEG score recompute
  22. 2026-06-24 02:14 UTCEG score recompute
  23. 2026-06-23 00:14 UTCEG score recompute
  24. 2026-06-21 22:12 UTCEG score recompute
  25. 2026-06-20 20:10 UTCEG score recompute
Show 3 more
  1. 2026-06-19 18:08 UTCEG score recompute
  2. 2026-06-18 16:07 UTCEG score recompute
  3. 2026-06-17 14:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-53765?
CVE-2026-53765 is a medium vulnerability published on June 17, 2026. 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…
When was CVE-2026-53765 disclosed?
CVE-2026-53765 was first published in the National Vulnerability Database on June 17, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53765 actively exploited?
CVE-2026-53765 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-53765?
CVE-2026-53765 has a CVSS v3 base score of 6.1 (NVD).
How do I remediate CVE-2026-53765?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53765, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53765

Explore →

Is Your Infrastructure Affected by CVE-2026-53765?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs