Skip to main content
Mallory
HighVulnerability

CVE-2026-123863: Node.js HTTP/2 Session Teardown Assertion Denial of Service

Published Nov 11, 2026 · Updated 1 day ago
Trending this week#59of 428,812 vulnerabilities
Mention activity · 30 days26 mentions · peak 14 in a dayToday
CVSS8.2High · v3
EPSS0.52%45th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123863CWE-617 · Reachable Assertion

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

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.
Activity feed

Recent activity

26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
phoenix security blogNews · Nov 12, 2026Node.js Vulnerabilities: TLS Key Leak and HTTP/2 Crash - Phoenix SecurityAn unauthenticated HTTP/2 denial-of-service vulnerability in Node.js, rated CVSS 8.2. A stream can outlive its session, causing the session destructor’s memory-counter assertion to fail and abort the process. Exploitation works over encrypted or cleartext HTTP/2 under a typical response-before-body-completion handler pattern. The advisory scopes affected releases to 24.x and 26.x, fixed in 24.22.3 and 26.13.1; a 22.x backport does not establish exploitability on that line. No supported workaround is available, but restricting listener access or removing unnecessary native HTTP/2 exposure is suggested as unvalidated risk reduction.Read more ↗mkd cirtNews · Nov 12, 2026Node.js поправи 16 ранливости, вклучувајќи HTTP/2-пропусти што можат да предизвикаат пад на серверите и истекување податоци од други конекции | MKD-CIRT | Национален центар за одговор на компјутерски инцидентиHigh-severity vulnerability allowing an unauthenticated client to crash Node.js HTTP/2 servers in branches 24.x and 26.x when a response is sent before the complete request body arrives. Exploitation works over TLS or unencrypted connections. Fixed releases are 24.22.3 and 26.13.1.Read more ↗the hacker newsNews · Nov 12, 2026Node.js Fixes 16 Flaws, Including HTTP/2 Bugs That Crash Servers and Leak Other Connections' DataAn unauthenticated client can crash Node.js HTTP/2 servers on the 24.x and 26.x release lines when servers respond before receiving the complete request body, behavior described as typical. Both TLS and cleartext connections are affected. Fixed releases are 24.22.3 and 26.13.1.Read more ↗tenable cloud security pluginsNews · Nov 12, 2026Alpine: nodejs: security update to 24.22.3-r0 | Tenable®An HTTP/2 denial-of-service vulnerability affecting Node.js 26.x since 26.9.0 and 24.x since 24.22.0. A stream retaining nghttp2 header buffers can outlive its session, causing a memory-accounting assertion to terminate the server. It is a variant not covered by the earlier CVE-2024-27983 fix.Read more ↗
+13 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity6Community discussion across Reddit, Mastodon, and other social sources.