CVE-2026-123862: Node.js zlib streaming denial of service after stream destruction
CVE-2026-123862 is a denial-of-service vulnerability in the Node.js zlib streaming API affecting the 22.x, 24.x, and 26.x release lines. The zlib.params() method queues a flush and completes its operation in the associated write callback. If a peer disconnects and pipeline() destroys the stream before that callback executes, Writable invokes the callback with an error. The callback ignores the error and asserts that the already-destroyed native handle still exists. The resulting ERR_INTERNAL_ASSERTION bypasses the stream error event, the params() callback, and the pipeline() callback, terminating the process. Only applications calling deflate.params() while streaming to a peer are affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
A peer can terminate the affected Node.js process by disconnecting during streaming compression, interrupting all requests and other work handled by that process. Normal stream and pipeline error handling does not prevent termination. No confidentiality or integrity impact is established.
Mitigation
If you can’t patch tonight, do this now.
Until patched, avoid calling deflate.params() while streaming compressed data to a peer. Where feasible, select compression parameters before beginning the peer-facing stream rather than changing them during transmission. Ordinary stream error listeners and params() or pipeline() callbacks do not catch this failure.
Remediation
Patch, then assume compromise.
Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the applicable release line. For distribution-managed installations, install the corresponding vendor security update; Alpine fixed packages include 22.23.5-r0 and 24.22.3-r0. The fix handles the zlib params callback safely after stream destruction.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-123862 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-123862 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123862?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123862.
- Is there a patch for CVE-2026-123862?
- Upgrade to Node.js 22.23.5, 24.22.3, or 26.13.1, or a later patched release in the applicable release line. For distribution-managed installations, install the corresponding vendor security update; Alpine fixed packages include 22.23.5-r0 and 24.22.3-r0.
- How severe is CVE-2026-123862?
- CVE-2026-123862 has a CVSS v3 score of 2.9 (Low) and an EPSS score of 0.15% (4th percentile) as of Nov 16, 2026.
Recent activity
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.