CVE-2026-69185
Socket.IO: Zero-attachment Memory Exhaustion
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Exploit likelihood
What each source reports
CVE List Score used
7.5
Socket.IO: Zero-attachment Memory Exhaustion
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.
- Record
CVE-2026-69185- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-20, CWE-754
- Updated
- 2026-11-02
EUVDEUVD-2026-52410
7.5
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.
- Record
EUVD-2026-52410- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
GitHub AdvisoriesGHSA-2m8v-j782-fhvr
7.5
Socket.IO: Zero-attachment Memory Exhaustion
Impact
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.
Patches
| Version range | Used by | Fixed version |
|------------------|--------------------------------------------|---------------|
| >=4.0.0 <4.2.7 | [email protected] and [email protected] | 4.2.7 |
| >=3.4.0 <3.4.5 | [email protected] | 3.4.5 |
| <3.3.6 | [email protected] | 3.3.6 |
Workarounds
There is no known workaround except upgrading to a safe version.
For more information
If you have any questions or comments about this advisory:
- Open a discussion here
- Record
GHSA-2m8v-j782-fhvr- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-20, CWE-754
- Updated
- 2026-11-02
NVD
7.5
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.
- Record
CVE-2026-69185- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-20, CWE-754
- Updated
- 2026-11-02
OSV
7.5
Socket.IO: Zero-attachment Memory Exhaustion
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.
- Record
CVE-2026-69185- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-20, CWE-754
- Updated
- 2026-11-02
OSVDEBIAN-CVE-2026-69185
7.5
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.
- Record
DEBIAN-CVE-2026-69185- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
Show 10 moreShow less
OSVGHSA-2m8v-j782-fhvr
7.5
Socket.IO: Zero-attachment Memory Exhaustion
Impact
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.
Patches
| Version range | Used by | Fixed version |
|------------------|--------------------------------------------|---------------|
| >=4.0.0 <4.2.7 | [email protected] and [email protected] | 4.2.7 |
| >=3.4.0 <3.4.5 | [email protected] | 3.4.5 |
| <3.3.6 | [email protected] | 3.3.6 |
Workarounds
There is no known workaround except upgrading to a safe version.
For more information
If you have any questions or comments about this advisory:
- Open a discussion here
- Record
GHSA-2m8v-j782-fhvr- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Weakness
- CWE-20, CWE-754
- Updated
- 2026-11-02
OSVUBUNTU-CVE-2026-69185
7.5
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.
- Record
UBUNTU-CVE-2026-69185- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H - Updated
- 2026-11-02
OSVCLSA-2026-1788863154 No score
TuxCare security update for socket.io-parser (1 CVE)
TuxCare rebuilt socket.io-parser to address 1 CVE. Fixed in 3.2.0-tuxcare.3.
- Record
CLSA-2026-1788863154- Updated
- 2026-11-02
OSVCLSA-2026-1788863169 No score
TuxCare security update for socket.io-parser (1 CVE)
TuxCare rebuilt socket.io-parser to address 1 CVE. Fixed in 3.1.3-tuxcare.2.
- Record
CLSA-2026-1788863169- Updated
- 2026-11-02
OSVCLSA-2026-1788863171 No score
TuxCare security update for socket.io-parser (1 CVE)
TuxCare rebuilt socket.io-parser to address 1 CVE. Fixed in 3.3.4-tuxcare.2.
- Record
CLSA-2026-1788863171- Updated
- 2026-11-02
OSVCLSA-2026-1791899634 No score
TuxCare security update for socket.io-parser (5 CVEs)
TuxCare rebuilt socket.io-parser to address 5 CVEs. Fixed in 2.3.1-tuxcare.1.
- Record
CLSA-2026-1791899634- Updated
- 2026-11-02
OSVCLSA-2026-1792599106 No score
TuxCare security update for socket.io-parser (5 CVEs)
TuxCare rebuilt socket.io-parser to address 5 CVEs. Fixed in 2.2.2-tuxcare.1.
- Record
CLSA-2026-1792599106- Updated
- 2026-11-02
OSVCLSA-2026-1792665531 No score
TuxCare security update for socket.io-parser (5 CVEs)
TuxCare rebuilt socket.io-parser to address 5 CVEs. Fixed in 2.2.4-tuxcare.1.
- Record
CLSA-2026-1792665531- Updated
- 2026-11-02
OSVCLSA-2026-1792666457 No score
TuxCare security update for socket.io-parser (2 CVEs)
TuxCare rebuilt socket.io-parser to address 2 CVEs. Fixed in 4.0.5-tuxcare.1.
- Record
CLSA-2026-1792666457- Updated
- 2026-11-02
OSVROOT-APP-NPM-CVE-2026-69185 No score
CVE-2026-69185 in socket.io-parser - Patched by Root
Root has patched CVE-2026-69185 in the socket.io-parser package for Root:npm. Multiple fixed versions available.
- Record
ROOT-APP-NPM-CVE-2026-69185- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
socket.io-parsernpm |
4.0.0 up to 4.2.7 | 4.2.7 |
socket.io-parsernpm |
3.4.0 up to 3.4.5 | 3.4.5 |
socket.io-parsernpm |
before 3.3.6 | 3.3.6 |
socket.io-parserTuxCare:npm |
3.2.0-tuxcare.0 up to 3.2.0-tuxcare.3, plus listed versions 3.2.03.2.0-tuxcare.13.2.0-tuxcare.2 |
3.2.0-tuxcare.3 |
socket.io-parserTuxCare:npm |
3.1.3-tuxcare.0 up to 3.1.3-tuxcare.2, plus listed versions 3.1.33.1.3-tuxcare.1 |
3.1.3-tuxcare.2 |
socket.io-parserTuxCare:npm |
3.3.4-tuxcare.0 up to 3.3.4-tuxcare.2, plus listed versions 3.3.43.3.4-tuxcare.1 |
3.3.4-tuxcare.2 |
socket.io-parserTuxCare:npm From an advisory covering 5 CVEs |
2.3.1-tuxcare.0 up to 2.3.1-tuxcare.1, plus listed versions 2.3.1 |
2.3.1-tuxcare.1 |
socket.io-parserTuxCare:npm From an advisory covering 5 CVEs |
2.2.2-tuxcare.0 up to 2.2.2-tuxcare.1, plus listed versions 2.2.2 |
2.2.2-tuxcare.1 |
socket.io-parserTuxCare:npm From an advisory covering 5 CVEs |
2.2.4-tuxcare.0 up to 2.2.4-tuxcare.1, plus listed versions 2.2.4 |
2.2.4-tuxcare.1 |
socket.io-parserTuxCare:npm From an advisory covering 2 CVEs |
4.0.5-tuxcare.0 up to 4.0.5-tuxcare.1, plus listed versions 4.0.5 |
4.0.5-tuxcare.1 |
Show 11 moreShow less
| Package | Affected | Fixed |
|---|---|---|
node-socket.io-parserDebian:12 |
All versions, plus listed versions 4.2.1+~3.1.0-24.2.1+~3.1.0-34.2.1+~3.1.0-44.2.4+~3.1.2-14.2.4+~3.1.2-2 |
None known |
node-socket.io-parserDebian:13 |
All versions, plus listed versions 4.2.1+~3.1.0-34.2.1+~3.1.0-44.2.4+~3.1.2-14.2.4+~3.1.2-2 |
None known |
node-socket.io-parserDebian:14 |
before 4.2.4+~3.1.2-1, plus listed versions 4.2.1+~3.1.0-34.2.1+~3.1.0-4 |
4.2.4+~3.1.2-1 |
socket.io-parserRoot:npm |
before 4.2.4-aikido.2 | 4.2.4-aikido.2 |
@rootio/socket.io-parserRoot:npm |
before 4.2.4-root.io.2 | 4.2.4-root.io.2 |
node-socket.io-parserUbuntu:18.04:LTS |
All versions, plus listed versions 2.3.1-1 |
None known |
node-socket.io-parserUbuntu:20.04:LTS |
All versions, plus listed versions 3.3.0-13.4.0-1 |
None known |
node-socket.io-parserUbuntu:22.04:LTS |
All versions, plus listed versions 4.0.2-14.1.1+~3.0.0-14.1.2+~3.0.0-1 |
None known |
node-socket.io-parserUbuntu:24.04:LTS |
All versions, plus listed versions 4.2.1+~3.1.0-3 |
None known |
node-socket.io-parserUbuntu:26.10 |
All versions, plus listed versions 4.2.1+~3.1.0-44.2.4+~3.1.2-14.2.4+~3.1.2-2 |
None known |
node-socket.io-parserUbuntu:26.04:LTS |
All versions, plus listed versions 4.2.1+~3.1.0-34.2.1+~3.1.0-4 |
None known |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| first indexed | CVE List, EUVD, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2026-69185 is a high vulnerability (CVSS 7.5) in Socketio Socket.io, published August 3, 2026. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.63%, the 50th percentile. Fixed in socket.io-parser 4.2.7.
References
github.com/socketio/socket.io/security/advisories/GHSA-2m8v-j782-fhvr
github.com/socketio/socket.io/commit/7c6ef571a00656718e9e05e3b948fd1758b2a7b4
github.com/socketio/socket.io/commit/9c6323e5cde41bd75df3379b5fc9293664a5f240
github.com/socketio/socket.io/commit/ced94ffa3ac020a8f3c14eb98a3bf34acb14d291
github.com/advisories/GHSA-2m8v-j782-fhvr
github.com/CVEProject/cvelistV5/tree/main/cves/2026/69xxx/CVE-2026-69185.json