CVE-2026-59725

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 72% 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
Trending — Patch released this week
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

Socket.IO enables bidirectional and low-latency communication for every platform. From 4.1.0 before 6.6.7, Engine.IO protocol v4 polling transport does not properly close the HTTP response for invalid binary POST requests with Content-Type: application/octet-stream, allowing an unauthenticated attacker to exhaust server-side connections and sockets. This issue is fixed in version 6.6.7.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
27.6%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 10, 2026

Advisory Details (3)

Auto-updated Jul 8, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Engine.IO Polling Transport Connection Exhaustion · Advisory · socketio/socket.io · GitHub

https://github.com/socketio/socket.io/security/advisories/GHSA-r635-g3xr-vw7x
github_release Patch Available

[email protected]

Patch available: socketio/socket.io [email protected]

https://github.com/socketio/socket.io/releases/tag/[email protected]
github_commit Patch Available

commit fc11285e1496 (socketio/socket.io)

Patch available: socketio/socket.io [email protected] (contains commit fc11285e1496)

https://github.com/socketio/socket.io/commit/fc11285e14964c2132d122164bf130c355f60671

Vendor Advisories for CVE-2026-59725(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdotnet8-0-main-8.0.128-1.1.hum12026-07-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 18× in last 7d / 18× 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-12 05:46 UTCEPSS rescore
  2. 2026-07-12 00:11 UTCEG score recompute
  3. 2026-07-12 00:11 UTCVendor advisory
  4. 2026-07-11 12:40 UTCEG score recompute
  5. 2026-07-11 12:40 UTCVendor advisory
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-11 01:11 UTCEG score recompute
  9. 2026-07-11 01:11 UTCVendor advisory
  10. 2026-07-10 13:42 UTCEG score recompute
  11. 2026-07-10 13:42 UTCVendor advisory
  12. 2026-07-10 02:13 UTCEG score recompute
  13. 2026-07-09 19:10 UTCEPSS rescore
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 14:45 UTCEG score recompute
  16. 2026-07-09 03:15 UTCEG score recompute
  17. 2026-07-08 15:46 UTCEG score recompute
  18. 2026-07-08 15:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-59725?
CVE-2026-59725 is a high vulnerability published on July 8, 2026. Socket.IO enables bidirectional and low-latency communication for every platform. From 4.1.0 before 6.6.7, Engine.IO protocol v4 polling transport does not properly close the HTTP response for invalid binary POST requests with Content-Type: application/octet-stream, allowing an unauthenticated…
When was CVE-2026-59725 disclosed?
CVE-2026-59725 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-59725 actively exploited?
CVE-2026-59725 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-59725?
CVE-2026-59725 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59725?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59725, 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

Explore the affected products and dependency analysis for CVE-2026-59725

Explore →

Is Your Infrastructure Affected by CVE-2026-59725?

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

Start Free Scan →Browse All CVEs