CVE-2026-69185

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% (48th percentile of EPSS-scored CVEs). 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.6%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 4.2.7, 3.4.5, and 3.3.6, a specially crafted Socket.IO packet can make the server wait for a large number of binary attachments and buffer them, which can be exploited to make the server run out of memory. This vulnerability is fixed in 4.2.7, 3.4.5, and 3.3.6.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.6%
EPSS %ILE
48th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 3, 2026

Last Modified

September 10, 2026

Advisory Details (4)

Auto-updated Aug 3, 2026
Patch available. Sources: github, github_commit.
github_commit Patch Available

commit ced94ffa3ac0 (socketio/socket.io)

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

https://github.com/socketio/socket.io/commit/ced94ffa3ac020a8f3c14eb98a3bf34acb14d291
github_commit Patch Available

commit 9c6323e5cde4 (socketio/socket.io)

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

https://github.com/socketio/socket.io/commit/9c6323e5cde41bd75df3379b5fc9293664a5f240
github_commit Patch Available

commit 7c6ef571a006 (socketio/socket.io)

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

https://github.com/socketio/socket.io/commit/7c6ef571a00656718e9e05e3b948fd1758b2a7b4
github Patch Available

Zero-attachment Memory Exhaustion · Advisory · socketio/socket.io · GitHub

https://github.com/socketio/socket.io/security/advisories/GHSA-2m8v-j782-fhvr

Vendor Advisories for CVE-2026-69185(1)

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

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
node-socket.io-parser4.0.2-1 ... 4.2.1+~3.1.0-4 (8 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
node-socket.io-parser4.2.1+~3.1.0-2, 4.2.1+~3.1.0-3, 4.2.1+~3.1.0-4, 4.2.4+~3.1.2-1, 4.2.4+~3.1.2-2
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
node-socket.io-parser4.2.1+~3.1.0-3, 4.2.1+~3.1.0-4, 4.2.4+~3.1.2-1, 4.2.4+~3.1.2-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
node-socket.io-parser4.2.1+~3.1.0-3, 4.2.1+~3.1.0-4
  • every version up to 4.2.4+~3.1.2-1: fixed in 4.2.4+~3.1.2-1
—
npm(1)
PackageVulnerable rangeFix by version rangeDependents
socket.io-parser—
  • 4.0.0 up to 4.2.7: fixed in 4.2.7
  • 3.4.0 up to 3.4.5: fixed in 3.4.5
  • every version up to 3.3.6: fixed in 3.3.6
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 46× 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 111 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Same product

4 shown

Debian:11:node-socket.io-parser · Debian:12:node-socket.io-parser · npm:socket.io-parser

Frequently asked(5)

What is CVE-2026-69185?
CVE-2026-69185 is a high vulnerability published on August 3, 2026. Socket.IO enables bidirectional and low-latency communication for every platform. Prior to 4.2.7, 3.4.5, and 3.3.6, a specially crafted Socket.IO packet can make the server wait for a large number of binary attachments and buffer them, which can be exploited to make the server run out of memory.…
When was CVE-2026-69185 disclosed?
CVE-2026-69185 was first published on August 3, 2026, with the most recent update on September 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-69185 actively exploited?
CVE-2026-69185 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-69185?
CVE-2026-69185 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-69185?
A fix for CVE-2026-69185 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-69185 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-69185?

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

Book a Demo →Browse All CVEs