CVE-2026-123865: Node.js is vulnerable to an HTTP/2 memory and file-descriptor leak via a protocol error during session shutdown
CVE-2026-123865 key facts
- CISA KEV
- Not listed (catalogue checked )
- Highest advisory rating
- High
- CVSS base score
- 7.5 (NetApp), 7.5 (Red Hat)
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H· base score 7.5, scored by openjsAttack vector: network. Attack complexity: low. 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.62% chance of exploitation in the next 30 days (50th percentile). FIRST EPSS, .
- CISA SSVC
- Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
- Fixed releases
- Red Hat: nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-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 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-123865; each belongs to its advisory, not to every product listed. How records are collected and checked.
Description
An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js's HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Text from the CVE.org record (openjs).
How do I fix CVE-2026-123865?
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.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-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
- 1. Terminate HTTP/2 at an upstream reverse proxy: Configure an edge reverse proxy (such as HAProxy, Envoy, or Apache HTTP Server) to handle client HTTP/2 traffic and proxy requests to the backend Node.js application over standard HTTP/1.1. Alternatively, if HTTP/2 capabilities are not required by the application, configure the Node.js application to use the standard `http` or `https` modules instead of `http2`. 2. Restrict network access using firewalld: If direct exposure cannot be avoided, limit network access to the Node.js HTTP/2 port so only trusted internal clients or reverse proxies can reach it: firewall-cmd --permanent --zone=trusted --add-source= firewall-cmd --permanent --zone=trusted --add-port= /tcp firewall-cmd --reload Caveats: Restricting access via firewall rules blocks untrusted external networks from communicating directly with the service. Reloading firewalld applies changes immediately. Reconfiguring the Node.js application or underlying service settings requires restarting the Node.js process, which will temporarily interrupt active client connections. (Red Hat)
Vendor advisories for CVE-2026-123865
NetApp
1 advisory- Advisory severityHigh7.5
High [CVE-2026-123865] Node.js Vulnerability in NetApp Products
NTAP-20261120-0009Source published Source updated
Node.js versions 22.x prior to 22.23.5, 24.x prior to 24.22.3 and 26.x prior to 26.13.1 are susceptible to a vulnerability which when successfully exploited could allow an unauthenticated remote attacker to persistently consume server memory and file descriptors, potentially exhausting system resources and affecting normal server operations. Successful exploitation of this vulnerability could lead to Denial of Service (DoS). NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. 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
- 22.23.5
- 24.22.3
- 26.13.1
- 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 severityHigh7.5
High [CVE-2026-123865] Denial of service via HTTP/2 session resource leak during shutdown
CVE-2026-123865Source published Source updated
Denial of service via HTTP/2 session resource leak during shutdown. Red Hat rates this important (CVSS 7.5). Weakness: CWE-400. Red Hat lists fixing advisory RHSA-2026:99433 with package nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.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.5.2.3.2.3.1.hum1
- nodejs22-main-22.23.5-2.3.2.3.1.hum1
- nodejs26-main-11.20.0-1.26.13.1.0.1.hum1
3 more entries in the full advisory.
- Mitigation guidance
- 1. Terminate HTTP/2 at an upstream reverse proxy: Configure an edge reverse proxy (such as HAProxy, Envoy, or Apache HTTP Server) to handle client HTTP/2 traffic and proxy requests to the backend Node.js application over standard HTTP/1.1. Alternatively, if HTTP/2 capabilities are not required by the application, configure the Node.js application to use the standard `http` or `https` modules instead of `http2`. 2. Restrict network access using firewalld: If direct exposure cannot be avoided, limit network access to the Node.js HTTP/2 port so only trusted internal clients or reverse proxies can reach it: firewall-cmd --permanent --zone=trusted --add-source=<TRUSTED_IP_OR_SUBNET> firewall-cmd --permanent --zone=trusted --add-port=<NODE_PORT>/tcp firewall-cmd --reload Caveats: Restricting access via firewall rules blocks untrusted external networks from communicating directly with the service. Reloading firewalld applies changes immediately. Reconfiguring the Node.js application or underlying service settings requires restarting the Node.js process, which will temporarily interrupt active client connections.
References
Timeline
- CVE record published
- First vendor advisory listed by VulniPulse
- CVE record last updated
More NetApp advisories
CVE-2026-114949Nov 20, 2026November 2026 MySQL Vulnerabilities in NetApp ProductsCVE-2026-123863Nov 20, 2026Node.js Vulnerability in NetApp ProductsCVE-2026-123828Nov 20, 2026Node.js Vulnerability in NetApp ProductsCVE-2026-123863Nov 20, 2026Node.js Vulnerability in NetApp ProductsCVE-2026-123868Nov 20, 2026Node.js Vulnerability in NetApp ProductsCVE-2026-53006Nov 20, 2026Linux Kernel 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.