CVE-2026-69185 json
Socket.IO: Zero-attachment Memory Exhaustion
published 2026-08-03 3 mo ago modified 2026-10-23 16 d ago also GHSA-2m8v-j782-fhvr , EUVD-2026-52410
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm socket.io-parser 3.3.6, 3.4.5, 4.2.7
- node-socket.io-parser Debian 14 4.2.4+~3.1.2-1
debian advisories DEBIAN-CVE-2026-69185
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-69185 updated cvss 7.5
socket.io-parser: Socket.IO: Denial of Service via memory exhaustion from crafted packets
-
Red Hat Enterprise Linux AI (RHEL AI) 3 rhelai3/bootc-cuda-rhel9, rhelai3/bootc-rocm-rhel9, rhelai3/bootc-gaudi-rhel9, rhelai3/disk-image-cuda-rhel9affected: no fix available, no fix planned “Will not fix”
-
Red Hat Hardened Images dotnet8.0 8.0.129-2.hum1, grafana12.4 12.4.6-0.2.hum1, grafana13.1 13.1.1-0.3.hum1not affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 3 mo ago
Exploit prediction
0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | socket.io-parser | >=4.0.0, <4.2.7 >=3.4.0, <3.4.5 <3.3.6 |
4.2.7 3.4.5 3.3.6 |
Affected products
- socketio socket.io
Classification
References
-
github.com
/socketio/socket.io/commit/7c6ef571a00656718e9e05e3b948fd1758b2a7b4
web
-
github.com
/socketio/socket.io/commit/9c6323e5cde41bd75df3379b5fc9293664a5f240
web
-
github.com
/socketio/socket.io/commit/ced94ffa3ac020a8f3c14eb98a3bf34acb14d291
web
-
github.com
/socketio/socket.io/security/advisories/GHSA-2m8v-j782-fhvr
web
-
github.com
/socketio/socket.io
package
Sources
- CVE List CVE-2026-69185
- GitHub Advisory GHSA-2m8v-j782-fhvr
- NVD CVE-2026-69185
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.