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.3%, 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
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%CVSS: 7.5Exploit: None knownExposed: 0

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

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.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%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

August 3, 2026

Last Modified

August 3, 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 rangeFixed inDependents
node-socket.io-parser4.0.2-1 ... 4.2.1+~3.1.0-4 (8 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
node-socket.io-parser4.2.1+~3.1.0-2, 4.2.1+~3.1.0-3, 4.2.1+~3.1.0-4——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
node-socket.io-parser4.2.1+~3.1.0-3, 4.2.1+~3.1.0-4——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
node-socket.io-parser4.2.1+~3.1.0-3, 4.2.1+~3.1.0-4——
npm(1)
PackageVulnerable rangeFixed inDependents
socket.io-parser—3.3.6—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 40× 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-08-21 05:20 UTCEG score recompute
  2. 2026-08-20 22:56 UTCEPSS rescore
  3. 2026-08-19 18:57 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 18:20 UTCEG score recompute
  6. 2026-08-18 13:49 UTCEPSS rescore
  7. 2026-08-18 13:49 UTCEPSS rescore
  8. 2026-08-17 17:30 UTCEG score recompute
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 18:35 UTCEG score recompute
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-16 14:56 UTCEPSS rescore
  13. 2026-08-16 07:07 UTCEG score recompute
  14. 2026-08-16 02:15 UTCEPSS rescore
  15. 2026-08-15 08:13 UTCEG score recompute
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 09:18 UTCEG score recompute
  18. 2026-08-13 22:00 UTCEPSS rescore
  19. 2026-08-12 22:57 UTCEG score recompute
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-12 00:02 UTCEG score recompute
  22. 2026-08-11 01:08 UTCEG score recompute
  23. 2026-08-11 00:00 UTCEPSS rescore
  24. 2026-08-09 14:47 UTCEG score recompute
  25. 2026-08-09 13:47 UTCEPSS rescore
Show 15 more
  1. 2026-08-09 03:20 UTCEG score recompute
  2. 2026-08-08 16:37 UTCEPSS rescore
  3. 2026-08-07 16:58 UTCEG score recompute
  4. 2026-08-06 18:04 UTCEG score recompute
  5. 2026-08-06 13:47 UTCEPSS rescore
  6. 2026-08-06 06:37 UTCEG score recompute
  7. 2026-08-05 19:17 UTCEPSS rescore
  8. 2026-08-05 19:17 UTCEPSS rescore
  9. 2026-08-04 20:16 UTCEG score recompute
  10. 2026-08-04 15:10 UTCEPSS rescore
  11. 2026-08-03 21:20 UTCEG score recompute
  12. 2026-08-03 20:43 UTCEG score recompute
  13. 2026-08-03 20:19 UTCEG score recompute
  14. 2026-08-03 19:38 UTCEG score recompute
  15. 2026-08-03 19:38 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

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 in the National Vulnerability Database on August 3, 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% probability of exploitation in the next 30 days, which ranks it in the top 72.2% of all scored CVEs.
What is the CVSS score of CVE-2026-69185?
CVE-2026-69185 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-69185?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-69185, 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-69185

Explore →

Is Your Infrastructure Affected by CVE-2026-69185?

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

Start Free Scan →Browse All CVEs