CVE-2026-69185: Socket.IO: Zero-attachment Memory Exhaustion

Published Aug 3, 2026
·
Updated

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 | socket.io@4.x and socket.io-client@4.x | 4.2.7 | | >=3.4.0 <3.4.5 | socket.io@2.x | 3.4.5 | | <3.3.6 | socket.io-client@2.x | 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

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
npm/socket.io-parser<3.3.6
3.3.6
npm/socket.io-parser>=3.4.0<3.4.5
3.4.5
npm/socket.io-parser>=4.0.0<4.2.7
4.2.7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/socket.io-parser to a version that resolves this vulnerability.

    Fixed in 3.3.6
  2. Upgrade

    Upgrade npm/socket.io-parser to a version that resolves this vulnerability.

    Fixed in 3.4.5
  3. Upgrade

    Upgrade npm/socket.io-parser to a version that resolves this vulnerability.

    Fixed in 4.2.7
  4. Upgrade

    Upgrade socket.io/socket.io to a version that resolves this vulnerability.

    Fixed in 4.2.7
  5. Upgrade

    Upgrade socket.io/socket.io to a version that resolves this vulnerability.

    Fixed in 3.4.5
  6. Upgrade

    Upgrade socket.io/socket.io to a version that resolves this vulnerability.

    Fixed in 3.3.6

Event History

Aug 3, 2026
CVE Published
via MITRE·07:09 PM
Data Sourced
via MITRE·07:09 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·07:09 PM
Data Sourced
via GitHub·07:09 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·08:17 PM
DescriptionSeverityWeakness
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-69185?

The severity of CVE-2026-69185 is rated as high with a score of 7.5.

2

What systems are affected by CVE-2026-69185?

CVE-2026-69185 affects systems using the Socket.IO library due to memory exhaustion vulnerabilities.

3

How do I mitigate CVE-2026-69185?

Mitigation for CVE-2026-69185 involves updating to the fixed versions of Socket.IO that address the memory exhaustion issue.

4

What is the impact of CVE-2026-69185?

The impact of CVE-2026-69185 is that a specially crafted Socket.IO packet can lead to server memory exhaustion.

5

Is there any patch available for CVE-2026-69185?

Yes, CVE-2026-69185 has specific patches available that users can apply by updating Socket.IO to the appropriate fixed version.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203