Skip to main content
VulnerabilityPublished Updated

CVE-2026-123868: Nodejs · An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA

Affects nodejsSource GCVE Database

0
Compare
Authoritative record:CVE-2026-123868· Medium 5.9

Not known to be exploited · CVSS 5.9 Medium.

Data as of 13 Nov 2026, 22:04 UTC

CVSS 3.0 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.05.9
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10nodejspkg:deb/ubuntu/nodejs?arch=source&distro=stonkingOther threatsAffected
  • 22.22.1+dfsg+~cs22.19.15-1ubuntu1 – 24.19.0+dfsg+~cs24.13.3-1ubuntu1
4 affected builds
Fixed in–
Ubuntu 26.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=resoluteOther threatsAffected
  • 20.19.4+dfsg-1 – 22.22.1+dfsg+~cs22.19.15-1ubuntu1
6 affected builds
Fixed in–
Ubuntu 24.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=nobleOther threatsAffected
  • 18.13.0+dfsg1-1ubuntu2 – 18.19.1+dfsg-6ubuntu5
5 affected builds
Fixed in–
Ubuntu Pro 22.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/jammyOther threatsAffected
  • 12.22.5~dfsg-5ubuntu1 – 12.22.9~dfsg-1ubuntu3.6+esm2
12 affected builds
Fixed in–
Ubuntu Pro 20.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/focalOther threatsAffected
  • 10.15.2~dfsg-2ubuntu1 – 10.19.0~dfsg-3ubuntu1.6+esm2
10 affected builds
Fixed in–
Ubuntu Pro 18.04 LTSnodejspkg:deb/ubuntu/nodejs?arch=source&distro=esm-apps/bionicOther threatsAffected
  • 6.11.4~dfsg-1ubuntu1 – 8.10.0~dfsg-2ubuntu0.4+esm6
15 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.

References

Community reviews

Loading reviews…