CVSS 3.0
7.5 highCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVE-2026-126051 Node.js is vulnerable to a remotely triggerable uncaught exception in TLS servers via deferred handshake callbacks
High (7.5) in nodejs node. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.
On this page
A deferred-callback use-after-destroy in Node.js TLS server handshake handling allows a remote, unauthenticated attacker to terminate the server process. When a TLS server uses any of the SNICallback, OCSPRequest, newSession, or resumeSession hooks, or server.addContext(), the corresponding OpenSSL callbacks are deferred, and the deferred code does not handle the underlying socket being destroyed between scheduling and execution. By sending a client hello that reaches the vulnerable path (for example, no SNI together with an OCSP request) followed by padding and a socket FIN, an attacker makes OpenSSL deliver the client hello and the end-of-file in the same tick, so the socket is destroyed before the deferred callback runs and the process raises an uncaught exception instead of emitting an 'error' event. This vulnerability affects Node.js 26.x and 24.x.
Severity
- EPSS
- 0.8% estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-476 NULL Pointer Dereference
- OWASP Top 10
- A10:2025 Mishandling of Exceptional Conditions
- Published
- Modified
- Assigned by
- openjs (CNA)
- NVD analysis
- Awaiting analysis
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126051 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126051?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126051?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126051 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Badge for a README or a site
An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:
[](https://cve.bz/cve/CVE-2026-126051)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126051"><img src="https://cve.bz/cve/badge/CVE-2026-126051.svg" alt="CVE-2026-126051"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| nodejs node | from 24.0.0 before 24.22.3 |
| nodejs node | from 25.0.0 before 26.13.1 |
Fix and patched versions
- Red Hat, Alpine, Alpaquita, BellSoft Hardened Containers: fixed package versions per release
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | nodejs | no fix listed | DEBIAN-CVE-2026-126051 |
| Ubuntu | 24.04:LTS, 26.04:LTS, 26.10 and 5 more | nodejs | no fix listed | UBUNTU-CVE-2026-126051 |
| Red Hat | hummingbird:1 | nodejs22, nodejs22-bin, nodejs22-docs and 4 more | 1:22.23.4-2.3.2.3.1.hum1 | RHSA-2026:93603 |
| Red Hat | hummingbird:1 | nodejs22-npm | 1:10.9.9-1.22.23.4.2.3.2.3.1.hum1 | RHSA-2026:93603 |
| Red Hat | hummingbird:1 | nodejs24, nodejs24-bin, nodejs24-docs and 3 more | 1:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm | 2:11.19.1-1.24.22.3.0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs24-npm-bin | 2:24.22.3-0.1.hum1 | RHSA-2026:99435 |
| Red Hat | hummingbird:1 | nodejs26, nodejs26-bin, nodejs26-docs and 4 more | 1:26.13.1-0.1.hum1 | RHSA-2026:99436 |
| Red Hat | hummingbird:1 | nodejs26-npm | 1:11.20.0-1.26.13.1.0.1.hum1 | RHSA-2026:99436 |
| Red Hat | hummingbird:1 | v8-12.4-devel | 3:12.4.254.21-1.22.23.4.2.3.2.3.1.hum1 | RHSA-2026:93603 |
| Alpine | v3.23, v3.24 | nodejs | 24.22.3-r0 | ALPINE-CVE-2026-126051 |
| Alpine | v3.24 | nodejs-current | 26.13.1-r0 | ALPINE-CVE-2026-126051 |
| Alpaquita | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-126051 |
| Alpaquita | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-126051 |
| BellSoft Hardened Containers | stream | nodejs24 | 24.22.3-r0 | BELL-CVE-2026-126051 |
| BellSoft Hardened Containers | stream | nodejs26 | 26.13.1-r0 | BELL-CVE-2026-126051 |
From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine · Alpaquita · BellSoft Hardened Containers.
Red Hat
Red Hat rates this Important.
Red Hat Product Security rates this vulnerability as an Important severity flaw because an unauthenticated remote attacker can terminate the Node.js process, leading to a complete denial of service. The issue specifically impacts applications where the Node.js server handles TLS handshakes directly and registers dynamic context or certificate hooks, such as SNI or session resumption callbacks. Deployments where TLS traffic is terminated upstream by a reverse proxy, load balancer, or OpenShift ingress controller do not execute the vulnerable handshake path in Node.js and are not exposed.
Prefer terminating TLS at a reverse proxy rather than in-process Node.js TLS. If SNICallback, OCSPRequest, newSession/resumeSession, or addContext hooks are unused, avoid configuring them on internet-facing TLS servers.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Hardened Images | nodejs22-main-10.9.9-1.22.23.4.2.3.2.3.1.hum1 | Fixed 2026-11-02 | RHSA-2026:93603 |
| Red Hat Hardened Images | nodejs22-main-22.23.4-2.3.2.3.1.hum1 | Fixed 2026-11-02 | RHSA-2026:93603 |
| Red Hat Enterprise Linux 10 | nodejs22 | Not affected | |
| Red Hat Enterprise Linux 10 | nodejs24 | Affected | |
| Red Hat Enterprise Linux 10 | nodejs26 | Affected | |
| Red Hat Enterprise Linux 8 | nodejs:22/nodejs | Not affected | |
| Red Hat Enterprise Linux 8 | nodejs:24/nodejs | Affected | |
| Red Hat Enterprise Linux 9 | nodejs:22/nodejs | Not affected | |
| Red Hat Enterprise Linux 9 | nodejs:24/nodejs | Affected | |
| Red Hat Enterprise Linux 9 | nodejs:26/nodejs | Affected | |
| Red Hat Hardened Images | hi/nodejs | Under investigation | |
| Red Hat Hardened Images | nodejs20 | Will not fix | |
| Red Hat Hardened Images | nodejs24 | Affected | |
| Red Hat Hardened Images | nodejs25 | Will not fix | |
| Red Hat Hardened Images | nodejs26 | Affected | |
| Red Hat Hardened Images | npm12 | Under investigation |
Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-126051.