CVE-2026-33151

socket.io allows an unbounded number of binary attachments

Published Mar 20, 2026 CVSS 4.0 · 8.7 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A specially crafted packet to the Socket.IO framework can force the server to wait for a large number of binary attachments and buffer them. The result is an out‑of‑memory condition that stops the server from processing new requests and effectively brings the service offline. This weakness is a classic memory exhaustion flaw and falls under CWE‑770. The impact is a denial of service, compromising availability rather than confidentiality or integrity.

Affected Systems

Socket.IO, versions prior to 3.3.5, 3.4.4, and 4.2.6, regardless of the underlying Node.js runtime. The affected component is the Socket.IO parser module, which accepts client packets over WebSocket or HTTP.

Risk and Exploitability

The issue carries a high severity CVSS score of 8.7. Its exploit probability is low (EPSS < 1%) and it is not listed in the CISA KEV catalog. The vulnerability is remotely accessible; an attacker only needs send a malicious packet over an open Socket.IO connection, without authentication. If exploited, the server would exhaust its memory pool, leading to a service crash or refusal to accept further requests.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Socket.IO to version 3.3.5, 3.4.4, or 4.2.6 or later.

Generated by OpenCVE AI on April 14, 2026 at 21:09 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-677m-j7p3-52f9 socket.io allows an unbounded number of binary attachments
History
Type Values Removed Values Added
First Time appeared Socket socket.io-parser
Weaknesses NVD-CWE-noinfo
CPEs cpe:2.3:a:socket:socket.io-parser:*:*:*:*:*:node.js:*:*
Vendors & Products Socket socket.io-parser
Metrics cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.3, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L'}

threat_severity

Moderate

Type Values Removed Values Added
First Time appeared Socket
Socket socket.io
Vendors & Products Socket
Socket socket.io
Type Values Removed Values Added
Description 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.
Title socket.io allows an unbounded number of binary attachments
Weaknesses CWE-20
CWE-754
References
Metrics cvssV4_0

{'score': 8.7, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N'}

Weaknesses
  • CWE-20

    Improper Input Validation

  • CWE-754

    Improper Check for Unusual or Exceptional Conditions

  • CWE-770

    Allocation of Resources Without Limits or Throttling

  • NVD-CWE-noinfo

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 23, 2026, 4:50 PM
Reserved
Mar 17, 2026, 9:17 PM
Status
Analyzed
Published
Mar 20, 2026, 9:17 PM
Modified
Jun 17, 2026, 10:37 AM
Severity
Moderate
Public date
Mar 20, 2026, 8:13 PM