CVE-2026-123868: Node.js HTTP/2 Memory Exhaustion Through Unaccounted Inbound DATA
CVE-2026-123868 is a memory-accounting vulnerability affecting Node.js 24.x and 26.x HTTP/2 servers. Each inbound DATA frame creates a JavaScript Buffer view in the receiving stream's readable queue. When the stream remains undrained, these views accumulate without being charged to current_session_memory_; socket read-buffer accounting applies only during parsing and is immediately released. Consequently, maxSessionMemory does not bound the retained queue, and Http2Session::CanAddStream does not reject additional streams based on that memory consumption. An unauthenticated client can exploit this accounting gap using numerous small DATA frames to exhaust server memory and cause denial of service.
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.
Remote attackers can exhaust server memory, degrading availability or causing process termination. One-byte DATA frames require approximately 10 bytes on the wire while retaining approximately 114 bytes on the server. A single stream on one connection can therefore retain hundreds of megabytes from tens of megabytes transmitted. The configured session-memory limit does not contain this growth or prevent additional stream admission. No confidentiality or integrity impact is established.
Mitigation
If you can’t patch tonight, do this now.
No specific vendor workaround is established. Reducing maxSessionMemory is not an effective mitigation because the vulnerable stream queue is excluded from the memory counter used to enforce that limit.
Remediation
Patch, then assume compromise.
Upgrade affected Node.js 24.x installations to 24.22.3 or a later patched release, and affected 26.x installations to 26.13.1 or a later patched release. The fix charges inbound DATA retained by streams to maxSessionMemory. For distribution-managed installations, apply the corresponding vendor security update; Alpine provides the 24.x update in 24.22.3-r0. Patch availability varies by distribution, so verify that the installed package explicitly includes the fix for CVE-2026-123868.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-123868 exploited in the wild?
- As of Nov 16, 2026, Mallory has no reports of CVE-2026-123868 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-123868?
- As of Nov 16, 2026, Mallory has found no public exploit for CVE-2026-123868.
- Is there a patch for CVE-2026-123868?
- Upgrade affected Node.js 24.x installations to 24.22.3 or a later patched release, and affected 26.x installations to 26.13.1 or a later patched release. The fix charges inbound DATA retained by streams to maxSessionMemory.
- How severe is CVE-2026-123868?
- CVE-2026-123868 has a CVSS v3 score of 5.9 (Medium) and an EPSS score of 0.48% (42nd percentile) as of Nov 16, 2026.
Recent activity
14 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.