CVE-2026-123863: Node.js is vulnerable to a remote HTTP/2 denial of service via a reachable assertion in Http2Session teardown
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-17 06:13 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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).
Description quoted from the CVE record (assigned by openjs, published 2026-11-11).
Weakness: Reachable Assertion
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality none, integrity low, availability high. CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H
Public exploit evidence (Exploit Observer)
Exploit Observer has no public exploit code naming this CVE. Check Exploit Observer for anything new.
Live scores
- EPSS
- 0.005
low predicted chance of attack - VEDAS
- 0.514
likely exploited - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Thin horizontal line: the “likely exploited” threshold (EPSS 0.10, VEDAS 0.5). Shaded “no data” areas are periods when cve-scores did not publish.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Nodejs node | from 24.0.0 before 24.22.3 from 25.0.0 before 26.13.1 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 24.22.3, 26.13.1.
Vendor guidance:
- https://nodejs.org/en/blog/vulnerability/november-2026-security-releases (vendor-advisory)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
Advisories on this CVE
References
Vendor advisories and patches
- https://nodejs.org/en/blog/vulnerability/november-2026-security-releases (vendor-advisory)
Other references
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners