CVE-2026-123868: Node.js is vulnerable to an HTTP/2 memory exhaustion denial of service via unaccounted inbound DATA on an undrained stream
CVE-2026-123868 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- Critical
- CVSS base score
- 5.9 (Red Hat)
- CVSS vector
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H· base score 5.9, scored by openjsAttack vector: network. Attack complexity: high. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: none. Integrity impact: none. Availability impact: high.- Weakness
- CWE-400 Uncontrolled Resource Consumption
- EPSS
- 0.48% chance of exploitation in the next 30 days (41st percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: no. Technical impact: partial. CISA, .
- Fixed releases
- Red Hat: nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.4.2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs24-main-11.19.1-1.24.22.3.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1, nodejs22-main-22.23.4-2.3.2.3.1.hum1 and 1 more in the advisory
- Assigned by
- openjs (CNA)
- CVE record published
- Listed by VulniPulse
- Record changed
Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-123868; each belongs to its advisory, not to every product listed. How records are collected and checked.
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.
Text from the CVE.org record (openjs).
How do I fix CVE-2026-123868?
Upgrade to a fixed release named by the vendor:
- Red Hat: nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.4.2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs24-main-11.19.1-1.24.22.3.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1, nodejs22-main-22.23.4-2.3.2.3.1.hum1
- To mitigate this issue, restrict access to the Node.js application to trusted networks using firewall controls, or deploy an upstream reverse proxy (such as HAProxy or NGINX) to terminate HTTP/2 traffic and forward requests to Node.js using HTTP/1.1. If the application is designed solely for local consumption, bind the listener to localhost (127.0.0.1). To restrict inbound traffic on the service port to trusted source addresses using firewalld: firewall-cmd --permanent --zone=trusted --add-source= firewall-cmd --permanent --zone=public --remove-port= /tcp firewall-cmd --reload Caveats: Restricting access via firewall rules prevents untrusted clients from connecting to the application. Terminating HTTP/2 at an upstream proxy may alter client-side multiplexing characteristics and requires proxy reconfiguration. Warning: Reloading firewall rules with 'firewall-cmd --reload' applies changes immediately and may disrupt active network connections. (Red Hat)
Vendor advisories for CVE-2026-123868
NetApp
1 advisory- Advisory severityCritical9.2
Critical [CVE-2026-101898 +79] November 2026 IBM Cognos Analytics Vulnerabilities in NetApp Products
NTAP-20261118-0008Source published Source updated
This bulletin covers 80 CVEs. The products, versions, score and guidance below describe the bulletin; check its source for applicability to this specific CVE.
There are vulnerabilities in multiple Open Source Software (OSS) components consumed by IBM Cognos Analytics versions 12.1.0 through 12.1.3 FP3, 12.0 through 12.0.4 FP3 and 11.2.0 through 11.2.4 IF7 which when successfully exploited could lead to disclosure of sensitive information, addition or modification of data, or Denial of Service (DoS). NetApp states there is no workaround available at this time.
- Affected products in this advisory
- No product details extracted. Check the source bulletin.
- Source-reported affected versions
- 12.1.0
- 12.1.3
- 12.0
- 12.0.4
2 more entries in the full advisory.
- Source-reported fixed versions
- No fixed-version detail extracted. This does not mean no fix exists.
- Mitigation guidance
- No mitigation guidance extracted; consult the source.
Red Hat
1 advisory- Advisory severityMedium5.9
Medium [CVE-2026-123868] Denial of service via HTTP/2 memory exhaustion
CVE-2026-123868Source published Source updated
Denial of service via HTTP/2 memory exhaustion. Red Hat rates this moderate (CVSS 5.9). Weakness: CWE-400. Red Hat lists fixing advisory RHSA-2026:93603 with package nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.4.2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs24-main-11.19.1-1.24.22.3.0.1.hum1. Affected product named by the advisory: Red Hat Hardened Images.
- Related products — impact not confirmed
- Red Hat Hardened Images
- Source-reported affected versions
- Affected-version details not available in this record.
- Source-reported fixed versions
- nodejs24-main-24.22.3-0.1.hum1
- nodejs22-main-10.9.9-1.22.23.4.2.3.2.3.1.hum1
- nodejs26-main-11.20.0-1.26.13.1.0.1.hum1
- nodejs24-main-11.19.1-1.24.22.3.0.1.hum1
3 more entries in the full advisory.
- Mitigation guidance
- To mitigate this issue, restrict access to the Node.js application to trusted networks using firewall controls, or deploy an upstream reverse proxy (such as HAProxy or NGINX) to terminate HTTP/2 traffic and forward requests to Node.js using HTTP/1.1. If the application is designed solely for local consumption, bind the listener to localhost (127.0.0.1). To restrict inbound traffic on the service port to trusted source addresses using firewalld: firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_CIDR> firewall-cmd --permanent --zone=public --remove-port=<PORT>/tcp firewall-cmd --reload Caveats: Restricting access via firewall rules prevents untrusted clients from connecting to the application. Terminating HTTP/2 at an upstream proxy may alter client-side multiplexing characteristics and requires proxy reconfiguration. Warning: Reloading firewall rules with 'firewall-cmd --reload' applies changes immediately and may disrupt active network connections.
References
Timeline
- CVE record published
- First vendor advisory listed by VulniPulse
- CVE record last updated
More NetApp advisories
CVE-2026-121810Nov 18, 2026NGINX Vulnerability in NetApp ProductsCVE-2026-113425Nov 18, 2026NGINX Vulnerability in NetApp ProductsCVE-2026-114946Nov 18, 2026Java SE Vulnerability in NetApp ProductsCVE-2026-114945Nov 18, 2026Java SE Vulnerability in NetApp ProductsCVE-2026-123634Nov 18, 2026NGINX Vulnerability in NetApp ProductsCVE-2026-114943Nov 18, 2026Java SE Vulnerability in NetApp Products
Get an email when NetApp publishes the next one.
See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.