All reports
High

nodejs: Node.js: Denial of service via HTTP/2 session resource leak during shutdown

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-123865

Probability of exploitation in the next 30 days: 0.62%

FIRST EPSS · 2026-11-19

Description

An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js's HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

A flaw was found in Node.js. An unauthenticated remote attacker can cause a Denial of Service (DoS) through resource exhaustion by permanently leaking server memory and file descriptors. By initiating a connection shutdown and sending a protocol-violating HTTP/2 frame, the internal protocol handler terminates the session without Node.js properly releasing the associated state. Over time, an attacker can accumulate dangling connections, ultimately exhausting server resources and disrupting service availability.