CVE-2026-33151: socket.io allows an unbounded number of binary attachments

Published Mar 18, 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.6 | socket.io@4.x and socket.io-client@4.x | 4.2.6 | | >=3.4.0 <3.4.4 | socket.io@2.x | 3.4.4 | | <3.3.5 | socket.io-client@2.x | 3.3.5 |

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 is an open source, real-time, bidirectional, event-based, communication framework. Prior to versions 3.3.5, 3.4.4, and 4.2.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 issue has been patched in versions 3.3.5, 3.4.4, and 4.2.6.

MITRE

Affected Software

7 affected componentsFixes available
npm/socket.io-parser>=4.0.0<4.2.6
4.2.6
npm/socket.io-parser>=3.4.0<3.4.4
3.4.4
npm/socket.io-parser<3.3.5
3.3.5
Socket Socket.io-parser Node.js<3.3.5
Socket Socket.io-parser Node.js>=3.4.0<3.4.4
Socket Socket.io-parser Node.js>=4.0.0<4.2.6
IBM watsonx.data intelligence<=5.2.2, 5.3.0, 5.3.1, 5.3.1-patch-1

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 4.2.6
  2. Upgrade

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

    Fixed in 3.4.4
  3. Upgrade

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

    Fixed in 3.3.5
  4. Upgrade

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

    Fixed in 3.3.5
  5. Upgrade

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

    Fixed in 3.4.4
  6. Upgrade

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

    Fixed in 4.2.6

Event History

Mar 18, 2026
Advisory Published
via GitHub·05:26 PM
Data Sourced
via GitHub·05:26 PM
DescriptionWeaknessAffected Software
Mar 20, 2026
CVE Published
via MITRE·08:13 PM
Data Sourced
via MITRE·08:13 PM
DescriptionWeakness
Data Sourced
via NVD·09:17 PM
RemedyDescriptionSeverityWeaknessAffected Software
Jun 24, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

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-33151?

CVE-2026-33151 has a high severity rating due to its potential to exhaust server memory.

2

How do I fix CVE-2026-33151?

You can fix CVE-2026-33151 by upgrading to socket.io-parser version 4.2.6, 3.4.4, or 3.3.5.

3

What is the impact of CVE-2026-33151?

CVE-2026-33151 allows attackers to exploit the server by sending large amounts of binary attachments, leading to memory exhaustion.

4

Which versions are affected by CVE-2026-33151?

Versions of socket.io-parser from 4.0.0 to 4.2.6, 3.4.0 to 3.4.4, and below 3.3.5 are affected by CVE-2026-33151.

5

Is CVE-2026-33151 patch available?

Yes, patches for CVE-2026-33151 have been released in the specified fixed versions of socket.io-parser.

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