CVE-2026-123862: Uncatchable Exception
Source GCVE Database
Not known to be exploited · CVSS 2.9 Low · fixed in 26.13.1 : update node when convenient.
Data as of 11 Nov 2026, 22:35 UTC
Thin evidence
One scorer or none| CNA (openjs) | CVSS 3.0 | 2.9 |
|---|
- Patch
- Available – fixed in 26.13.1, 24.22.3, 22.23.5
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.
What to do
Upgrade node to 26.13.1, 24.22.3 or 22.23.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
| nodejsnode | Affected
| Fixed in
|
npmnodepkg:npm/nodeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should avoid calling deflate.params() during streaming to a peer until a fix is available. Monitor the Node.js official advisories for updates and apply patches when released. Since this is a low-severity denial of service, mitigation may also include handling peer disconnections gracefully and avoiding use of the vulnerable API pattern.
Description
A vulnerability in the Node.js zlib streaming API allows an uncatchable exception to crash a process when a peer disconnects during compression. This occurs because zlib.params() queues a flush operation that completes in a callback, which asserts on a native handle that may no longer exist if the stream is destroyed, causing an internal assertion error that terminates the process. The issue affects Node.js versions 22.x, 24.x, and 26.x and requires the application to call deflate.params() while streaming to a peer, which is uncommon.