Socket.IO: Engine.IO Polling Transport Connection Exhaustion
Impact
An unauthenticated remote attacker can cause a denial of service in affected versions of engine.io by opening Engine.IO polling sessions and sending an invalid binary POST request with:
Content-Type: application/octet-stream
against an Engine.IO protocol v4 polling transport.
In the vulnerable code path, the server reports a transport error but does not properly close the HTTP response associated with the malformed request. As a result, the underlying HTTP connection may remain open, consuming one server-side socket/resource per crafted request.
An attacker can repeat this with many sessions to exhaust available HTTP connections, sockets, file descriptors, or related server resources, potentially preventing legitimate clients from connecting.
Patches
The issue was fixed in:
- engine.io
6.6.7
The fix ensures that invalid binary polling POST requests are explicitly rejected with an HTTP response and closed properly.
Users should upgrade to:
npm install engine.io@^6.6.7
or a later fixed version.
If using Socket.IO through the monorepo/packages, update to a Socket.IO release that depends on a fixed engine.io version.
Workarounds
If upgrading immediately is not possible, possible mitigations include:
- Block or reject polling
POSTrequests withContent-Type: application/octet-streamfor Engine.IO protocol v4 at a reverse proxy, load balancer, WAF, or application middleware. - Disable HTTP long-polling if your deployment can use WebSocket-only transport.
- Enforce strict request/connection timeouts at the HTTP server, reverse proxy, or load balancer.
- Apply per-IP rate limits and connection limits for Engine.IO endpoints.
- Restrict access to the Socket.IO/Engine.IO endpoint where feasible.
Example Socket.IO configuration to disable polling, if compatible with your clients:
const io = new Server(httpServer, {
transports: ["websocket"],
});
References
- Fix commit: https://github.com/socketio/socket.io/commit/fc11285e14964c2132d122164bf130c355f60671
- engine.io changelog entry for
6.6.7: https://github.com/socketio/socket.io/blob/main/packages/engine.io/CHANGELOG.md#667-2026-04-27 - socket.io repository: https://github.com/socketio/socket.io
- engine.io package: https://www.npmjs.com/package/engine.io
Software afectado
Haz clic en una tecnología para ver todas sus vulnerabilidades.
| Plataforma | Paquete | Versiones vulnerables | Corregida en |
|---|---|---|---|
| Paquete de npm | engine.io | >= 4.1.0, < 6.6.7 | 6.6.7 |
Referencias
- https://github.com/socketio/socket.io/security/advisories/GHSA-r635-g3xr-vw7x
- https://nvd.nist.gov/vuln/detail/CVE-2026-59725
- https://github.com/socketio/socket.io/commit/fc11285e14964c2132d122164bf130c355f60671
- https://github.com/socketio/socket.io
- https://github.com/socketio/socket.io/releases/tag/engine.io@6.6.7
- Vector CVSS
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H- Debilidad (CWE)
CWE-404- Plataforma
- npm
- Paquete
engine.io- Publicada
- 20.07.2026
- Actualizado
- 11.10.2026 10:22
Fuentes y licencias
OSV / GitHub Advisory Database - GHSA-r635-g3xr-vw7x - CC BY 4.0
Historial de vulnerabilidades: engine.io
Todas las vulnerabilidades publicadas de este paquete (Paquete de npm), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.
- Entradas en total
- 7
- Primera → última
- 01.2022 09.2026
- Sin corrección
- 0
- Explotada en ataques
- 0
Distribución por gravedad
- Alta 5
- Media 2
Divulgaciones por año
- 2022: 3
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 3
-
Socket.IO: Engine.IO Polling Transport Connection Exhaustion esta entrada
Identifica las vulnerabilidades de tu aplicación
Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.