CVE-2026-123865: Red Hat Denial of service via HTTP/2 session resource leak during shutdown
This Red Hat advisory covers CVE-2026-123865. Related products: Red Hat Hardened Images.
Key facts
- Vendor rating
- High, CVSS 7.5
- 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, .
- CISA KEV
- Not listed (catalogue checked )
- Fixed in
- 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 and 4 more below
- Source published
- Listed by VulniPulse
- Record changed
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Related products & platforms
Description
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.
Text from the source record.
How to fix CVE-2026-123865
Upgrade to a fixed release named by 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
- RHSA-2026:99433
Vendor 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.
CVE-2026-123865 in other vendors' advisories
- NetApp: NTAP-20261120-0009, high severity
More Red Hat Linux advisories
CVE-2026-125350Nov 10, 2026Use after free in XMLCVE-2026-114713Nov 8, 2026Command injection via unescaped message tagCVE-2026-90436Nov 6, 2026Remote code execution via insecure deserialization of SOAP fault messagesCVE-2026-123158Nov 5, 2026Password authentication bypass via password hash misinterpretationCVE-2026-115731Nov 3, 2026authenticated remote code execution via report event deserializationCVE-2026-119977Oct 31, 2026Arbitrary code execution via predictable upgrade staging paths
Get an email when Red Hat publishes the next one.
See Red Hat'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.