CVE-2026-123863: Node.js HTTP/2 Session Teardown Assertion Denial of Service
CVE-2026-123863 is a reachable assertion vulnerability in Node.js HTTP/2 session teardown affecting versions 24.22.0 through 24.22.2 and 26.9.0 through 26.13.0. An unauthenticated client can cause an Http2Stream retaining nghttp2-allocated header buffers to outlive its session. The stream is removed from the session's tracked stream set without being detached, leaving current_nghttp2_memory_ nonzero when ~Http2Session() executes. The CHECK_EQ(current_nghttp2_memory_, 0) assertion consequently fails and aborts the process. Exploitation works over TLS or cleartext when a request handler responds before the request body has ended. This is a variant of CVE-2024-27983 whose earlier fix detached only streams still tracked by the session.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
A single unauthenticated HTTP/2 request can terminate the affected Node.js server process, dropping its in-flight connections and interrupting service. Repeated exploitation can produce a sustained crash loop even where workers restart automatically. No confidentiality compromise or code execution is established for this vulnerability.
Mitigation
If you can’t patch tonight, do this now.
No supported workaround is identified. As interim risk reduction, prevent untrusted clients from reaching native Node.js HTTP/2 listeners. Terminating HTTP/2 at a reverse proxy and forwarding only HTTP/1.1 to Node.js can remove this attack path, provided no alternate HTTP/2 listeners remain reachable. Access restrictions and reduced HTTP/2 exposure are not substitutes for patching.
Remediation
Patch, then assume compromise.
Upgrade Node.js 24.x to version 24.22.3 or later, or Node.js 26.x to version 26.13.1 or later. The fix releases HTTP/2 header buffers when a stream is removed. For distribution-managed installations, apply the corresponding vendor security update. Rebuild and redeploy affected container images, restart running workloads, and verify that the active processes use the patched runtime.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-123863 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-123863 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123863?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123863.
- Is there a patch for CVE-2026-123863?
- Upgrade Node.js 24.x to version 24.22.3 or later, or Node.js 26.x to version 26.13.1 or later. The fix releases HTTP/2 header buffers when a stream is removed.
- How severe is CVE-2026-123863?
- CVE-2026-123863 has a CVSS v3 score of 8.2 (High) and an EPSS score of 0.52% (45th percentile) as of Nov 16, 2026.
Recent activity
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.