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.6%, top 52% 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 — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.5Exploit: None knownExposed: 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)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 13, 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(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatdotnet8-0-main-8.0.129-2.hum12026-07-21redhat
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.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
engine.io—6.6.7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 19× in last 7d / 107× 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.

Showing the most recent 100 of 175 total refreshes for this CVE.

  1. 2026-08-30 07:34 UTCEG score recompute
  2. 2026-08-30 07:34 UTCVendor advisory
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-27 21:50 UTCEG score recompute
  6. 2026-08-27 21:50 UTCVendor advisory
  7. 2026-08-27 14:25 UTCEPSS rescore
  8. 2026-08-27 01:30 UTCEG score recompute
  9. 2026-08-27 01:30 UTCVendor advisory
  10. 2026-08-26 14:46 UTCEPSS rescore
  11. 2026-08-26 08:24 UTCVendor advisory
  12. 2026-08-25 14:48 UTCEG score recompute
  13. 2026-08-25 14:48 UTCVendor advisory
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-25 03:02 UTCVendor advisory
  16. 2026-08-24 15:32 UTCEG score recompute
  17. 2026-08-24 15:32 UTCVendor advisory
  18. 2026-08-24 04:01 UTCVendor advisory
  19. 2026-08-23 14:17 UTCVendor advisory
  20. 2026-08-23 02:49 UTCVendor advisory
  21. 2026-08-22 15:19 UTCVendor advisory
  22. 2026-08-22 03:49 UTCEG score recompute
  23. 2026-08-22 03:49 UTCVendor advisory
  24. 2026-08-21 23:49 UTCEPSS rescore
  25. 2026-08-21 15:29 UTCVendor advisory
Show 75 more
  1. 2026-08-21 03:59 UTCEG score recompute
  2. 2026-08-21 03:59 UTCVendor advisory
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 15:37 UTCVendor advisory
  5. 2026-08-20 02:00 UTCEG score recompute
  6. 2026-08-20 02:00 UTCVendor advisory
  7. 2026-08-19 17:04 UTCEPSS rescore
  8. 2026-08-19 10:17 UTCVendor advisory
  9. 2026-08-18 22:28 UTCEG score recompute
  10. 2026-08-18 22:28 UTCVendor advisory
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-18 10:50 UTCVendor advisory
  13. 2026-08-17 22:29 UTCEG score recompute
  14. 2026-08-17 22:29 UTCVendor advisory
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-17 06:05 UTCVendor advisory
  17. 2026-08-16 18:12 UTCEG score recompute
  18. 2026-08-16 18:12 UTCVendor advisory
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 06:43 UTCEG score recompute
  21. 2026-08-16 06:43 UTCVendor advisory
  22. 2026-08-16 02:14 UTCEPSS rescore
  23. 2026-08-15 19:15 UTCVendor advisory
  24. 2026-08-15 07:47 UTCEG score recompute
  25. 2026-08-15 07:47 UTCVendor advisory
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 20:10 UTCVendor advisory
  28. 2026-08-14 08:42 UTCEG score recompute
  29. 2026-08-14 08:42 UTCVendor advisory
  30. 2026-08-13 22:00 UTCEPSS rescore
  31. 2026-08-13 21:13 UTCVendor advisory
  32. 2026-08-13 09:42 UTCVendor advisory
  33. 2026-08-12 22:14 UTCEG score recompute
  34. 2026-08-12 22:14 UTCVendor advisory
  35. 2026-08-12 13:51 UTCEPSS rescore
  36. 2026-08-12 10:46 UTCVendor advisory
  37. 2026-08-11 23:17 UTCEG score recompute
  38. 2026-08-11 23:17 UTCVendor advisory
  39. 2026-08-11 11:50 UTCVendor advisory
  40. 2026-08-11 00:21 UTCEG score recompute
  41. 2026-08-11 00:21 UTCVendor advisory
  42. 2026-08-11 00:00 UTCEPSS rescore
  43. 2026-08-10 12:52 UTCVendor advisory
  44. 2026-08-10 01:24 UTCVendor advisory
  45. 2026-08-09 13:56 UTCEG score recompute
  46. 2026-08-09 13:56 UTCVendor advisory
  47. 2026-08-09 13:46 UTCEPSS rescore
  48. 2026-08-09 02:28 UTCEG score recompute
  49. 2026-08-09 02:28 UTCVendor advisory
  50. 2026-08-08 16:37 UTCEPSS rescore
  51. 2026-08-08 15:00 UTCVendor advisory
  52. 2026-08-08 03:31 UTCEG score recompute
  53. 2026-08-08 03:31 UTCVendor advisory
  54. 2026-08-07 16:03 UTCVendor advisory
  55. 2026-08-07 04:35 UTCVendor advisory
  56. 2026-08-06 17:07 UTCEG score recompute
  57. 2026-08-06 17:07 UTCVendor advisory
  58. 2026-08-06 13:47 UTCEPSS rescore
  59. 2026-08-06 05:39 UTCEG score recompute
  60. 2026-08-06 05:39 UTCVendor advisory
  61. 2026-08-05 19:17 UTCEPSS rescore
  62. 2026-08-05 18:11 UTCVendor advisory
  63. 2026-08-05 06:42 UTCVendor advisory
  64. 2026-08-04 17:18 UTCEG score recompute
  65. 2026-08-04 17:18 UTCVendor advisory
  66. 2026-08-04 15:10 UTCEPSS rescore
  67. 2026-08-04 10:39 UTCEPSS rescore
  68. 2026-08-04 05:50 UTCVendor advisory
  69. 2026-08-03 18:22 UTCEG score recompute
  70. 2026-08-03 18:22 UTCVendor advisory
  71. 2026-08-03 10:36 UTCEPSS rescore
  72. 2026-08-03 06:54 UTCVendor advisory
  73. 2026-08-02 19:25 UTCVendor advisory
  74. 2026-08-02 07:57 UTCEG score recompute
  75. 2026-08-02 07:57 UTCVendor advisory

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 13, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 52.3% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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