CVE-2026-59724

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 6.5.0 before 6.6.7, Engine.IO servers with WebTransport enabled can resolve a crafted session ID such as __proto__ through an inherited property of the clients object during WebTransport upgrade handling, causing a TypeError and denial of service. 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 WebTransport SID DoS · Advisory · socketio/socket.io · GitHub

https://github.com/socketio/socket.io/security/advisories/GHSA-gr94-w7qr-f4j3
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 1fa1f46cd420 (socketio/socket.io)

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

https://github.com/socketio/socket.io/commit/1fa1f46cd420ac5b57bb4c04c959b58f3c79158c

Vendor Advisories for CVE-2026-59724(2)

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.hum12026-06-18redhat

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 13× in last 7d / 62× 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 198 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-59724?
CVE-2026-59724 is a high vulnerability published on July 8, 2026. Socket.IO enables bidirectional and low-latency communication for every platform. From 6.5.0 before 6.6.7, Engine.IO servers with WebTransport enabled can resolve a crafted session ID such as proto through an inherited property of the clients object during WebTransport upgrade handling, causing a…
When was CVE-2026-59724 disclosed?
CVE-2026-59724 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-59724 actively exploited?
CVE-2026-59724 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.2% of all scored CVEs.
What is the CVSS score of CVE-2026-59724?
CVE-2026-59724 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-59724?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-59724, 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-59724

Explore →

Is Your Infrastructure Affected by CVE-2026-59724?

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

Start Free Scan →Browse All CVEs