CVE-2026-69185

Socket.IO: Zero-attachment Memory Exhaustion

Published Aug 3, 2026 CVSS 3.1 · 7.5 High EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-2m8v-j782-fhvr Socket.IO: Zero-attachment Memory Exhaustion
History
Type Values Removed Values Added
First Time appeared Socket
Socket socket.io
Vendors & Products Socket
Socket socket.io
Type Values Removed Values Added
Metrics ssvc

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

Type Values Removed Values Added
Description 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.
Title Socket.IO: Zero-attachment Memory Exhaustion
Weaknesses CWE-20
CWE-754
References
Metrics 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'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Aug 3, 2026, 8:31 PM
Reserved
Aug 3, 2026, 4:00 PM
Status
Awaiting Analysis
Published
Aug 3, 2026, 8:17 PM
Modified
Oct 23, 2026, 9:10 PM
Severity
Important
Public date
Aug 3, 2026, 7:09 PM