Uncaught exception in engine.io
Impact
A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process.
events.js:292
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -104,
code: 'ECONNRESET',
syscall: 'read'
}This impacts all the users of the engine.io package, including those who uses depending packages like socket.io.
Patches
A fix has been released today (2022/11/20):
| Version range | Fixed version |
|---|---|
engine.io@3.x.y |
3.6.1 |
engine.io@6.x.y |
6.2.1 |
For socket.io users:
| Version range | engine.io version |
Needs minor update? |
|---|---|---|
socket.io@4.5.x |
~6.2.0 |
npm audit fix should be sufficient |
socket.io@4.4.x |
~6.1.0 |
Please upgrade to socket.io@4.5.x |
socket.io@4.3.x |
~6.0.0 |
Please upgrade to socket.io@4.5.x |
socket.io@4.2.x |
~5.2.0 |
Please upgrade to socket.io@4.5.x |
socket.io@4.1.x |
~5.1.1 |
Please upgrade to socket.io@4.5.x |
socket.io@4.0.x |
~5.0.0 |
Please upgrade to socket.io@4.5.x |
socket.io@3.1.x |
~4.1.0 |
Please upgrade to socket.io@4.5.x (see here) |
socket.io@3.0.x |
~4.0.0 |
Please upgrade to socket.io@4.5.x (see here) |
socket.io@2.5.0 |
~3.6.0 |
npm audit fix should be sufficient |
socket.io@2.4.x and below |
~3.5.0 |
Please upgrade to socket.io@2.5.0 |
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 an issue in
engine.io
Thanks to Jonathan Neve for the responsible disclosure.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | engine.io | < 3.6.1, >= 4.0.0, < 6.2.1 | 3.6.1, 6.2.1 |
References
- https://github.com/socketio/engine.io/security/advisories/GHSA-r7qp-cfhv-p84w
- https://nvd.nist.gov/vuln/detail/CVE-2022-41940
- https://github.com/socketio/engine.io/commit/425e833ab13373edf1dd5a0706f07100db14e3c6
- https://github.com/socketio/engine.io/commit/83c4071af871fc188298d7d591e95670bf9f9085
- https://github.com/socketio/engine.io
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H- Weakness (CWE)
CWE-248- Platform
- npm
- Package
engine.io- Disclosed
- 21.11.2022
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-r7qp-cfhv-p84w - CC BY 4.0
Vulnerability history: engine.io
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 7
- First → latest
- 01.2022 09.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- High 5
- Medium 2
Disclosures per year
- 2022: 3
- 2023: 1
- 2024: 0
- 2025: 0
- 2026: 3
-
Uncaught exception in engine.io this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.