Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 11 Nov 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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). | |
| Title | Node.js is vulnerable to a remote HTTP/2 denial of service via a reachable assertion in Http2Session teardown | |
| Weaknesses | CWE-617 | |
| References |
| |
| Metrics |
cvssV3_0
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: openjs
Published:
Updated: 2026-11-11T18:16:12.733Z
Reserved: 2026-11-06T16:12:44.473Z
Link: CVE-2026-123863
No data.
Status : Received
Published: 2026-11-11T19:17:32.577
Modified: 2026-11-11T19:17:32.577
Link: CVE-2026-123863
No data.
OpenCVE Enrichment
No data.
-
CWE-617
Reachable Assertion