Skip to main content
Mallory
MediumVulnerability

CVE-2026-123868: Node.js HTTP/2 Memory Exhaustion Through Unaccounted Inbound DATA

Published Nov 11, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days14 mentions · peak 7 in a dayToday
CVSS5.9Medium · v3
EPSS0.48%42nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-123868CWE-770

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.

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.

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.

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

Recent activity

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

View more in app →
tenable cloud security pluginsNews · Nov 12, 2026Alpine: nodejs: security update to 24.22.3-r0 | Tenable®Unknown. The advisory includes this CVE in the Node.js package update but provides no vulnerability-specific description.Read more ↗tenable cloud security pluginsNews · Nov 12, 2026Alpine: nodejs: security update to 22.23.5-r0 | Tenable®Referenced as a vulnerability covered by the Alpine nodejs security update. No vulnerability-specific technical details are provided. The prescribed update is nodejs and related packages version 22.23.5-r0 or later.Read more ↗tenable nessus pluginsNews · Nov 12, 2026Linux Distros Unpatched Vulnerability : CVE-2026-123868 | Tenable®An unauthenticated remote memory-exhaustion vulnerability in Node.js HTTP/2 handling. Queued inbound DATA frames retain JavaScript Buffer views without being counted toward session memory limits, allowing substantial memory amplification and denial of service. The maxSessionMemory setting does not constrain this growth or prevent new streams. The reference assigns a CVSS v3 base score of 5.9 and reports no vendor patch or known solution.Read more ↗tenable nessus pluginsNews · Nov 12, 2026Amazon Linux 2023 : nodejs24, nodejs24-devel, nodejs24-full-i1... | Tenable®Queued HTTP/2 DATA buffers are omitted from session memory accounting, allowing an unauthenticated client to grow retained memory without maxSessionMemory limiting it. One-byte DATA frames produce substantial memory amplification, and a single stream can retain hundreds of megabytes. Node.js 26.x and 24.x are affected.Read more ↗
+7 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.