Node
Node.js is vulnerable to a remote HTTP/2 denial of service via a reachable assertion in Http2Session teardown
A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the session's stream set but never detached, so when ~Http2Session() runs the memory accounting is nonzero and the CHECK_EQ(current_nghttp2_memory_, 0) assertion fails, terminating the process. The trigger needs only a default http2 server whose handler responds before the request body has ended, which is typical. It is a variant of CVE-2024-27983 that the earlier fix did not cover, because that fix only detached streams still tracked in the session. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 24.0.0, < 24.22.3
- >= 25.0.0, < 26.13.1
Fixed in 24.22.3, 26.13.1
Mitigation
Upgrade node to 24.22.3 or 26.13.1 or later.
References
- Vendor advisory nodejs.org/en/blog/vulnerability/november-2026…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.