All reports
Medium

nodejs: Node.js: Denial of service via abrupt disconnection during zlib compression

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2026-123862

Probability of exploitation in the next 30 days: 0.19%

FIRST EPSS · 2026-11-21

Description

An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream's error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

A flaw was found in Node.js. A remote peer can trigger a denial of service (DoS) by abruptly disconnecting while data is being compressed using the zlib streaming interface. Under specific conditions where stream settings are adjusted during active compression, a sudden disconnection causes an internal assertion failure. Because this error bypasses standard application error handlers, it terminates the Node.js process unexpectedly.