CVE-2026-126051: Node.js is vulnerable to a remotely triggerable uncaught exception in TLS servers via deferred handshake callbacks
nodejs · node
No distribution fix yet for RHEL 8/9/10, Debian 12/13, SLES 15 SP7/16.0/16.1, openSUSE Leap 16.0/16.1 · Affected: nodejs · Exploitation: not established
ExploitationNot established
Not in CISA KEV as of catalogue 2026.11.13 (13 Nov)
- In CISA KEV: not seen
- Exploited (reported): not seen
- Scanning observed: not seen
- Proof of concept public: not seen
- Not establishedNothing in the sources we check
Higher than 56% of scored CVEs
Not scored yet. NVD has not published a CVSS score.
DescriptionNVD
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.
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- nodejs
- Published
- November 2026
Fix status by distribution
From each distribution’s security tracker. Distributions we did not check are not listed.
- Red Hat Enterprise Linux 10Affected, no fix releasedchecked 15 Nov 09:30 UTC
- Red Hat Enterprise Linux 9Affected, no fix releasedchecked 15 Nov 09:30 UTC
- Red Hat Enterprise Linux 8Affected, no fix releasedchecked 15 Nov 09:30 UTC
- Ubuntu 26.04Under investigationchecked 15 Nov 09:30 UTC
- Ubuntu 24.04Under investigationchecked 15 Nov 09:30 UTC
- Ubuntu 22.04Under investigationchecked 15 Nov 09:30 UTC
- Debian 13Affected, no fix releasedchecked 15 Nov 09:30 UTC
- Debian 12Affected, no fix releasedchecked 15 Nov 09:30 UTC
- SUSE Linux Enterprise Server 16.1Affected, no fix releasedchecked 15 Nov 09:30 UTC
- SUSE Linux Enterprise Server 16.0Affected, no fix releasedchecked 15 Nov 09:30 UTC
- SUSE Linux Enterprise Server 15 SP7Affected, no fix releasedchecked 15 Nov 09:30 UTC
- openSUSE Leap 16.1Affected, no fix releasedchecked 15 Nov 09:30 UTC
- openSUSE Leap 16.0Affected, no fix releasedchecked 15 Nov 09:30 UTC
What changed
Debian status tracked since 14 Nov 2026. Red Hat status tracked since 14 Nov 2026. SUSE status tracked since 15 Nov 2026. Ubuntu status tracked since 14 Nov 2026.
- SUSE’s tracker lists openSUSE Leap 16.0 as affected, with no fix released SUSE
- SUSE’s tracker lists openSUSE Leap 16.1 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP6 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 15 SP7 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 16.0 as affected, with no fix released SUSE
- SUSE’s tracker lists SLES 16.1 as affected, with no fix released SUSE
- Debian’s tracker lists Debian 12 as affected, with no fix released Debian
- Debian’s tracker lists Debian 13 as affected, with no fix released Debian
- Red Hat’s tracker lists RHEL 10 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 8 as affected, with no fix released Red Hat
- Red Hat’s tracker lists RHEL 9 as affected, with no fix released Red Hat
- Ubuntu’s tracker lists Ubuntu 14.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 16.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 18.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 20.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 22.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 24.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu 26.04 as under investigation Ubuntu
- Ubuntu’s tracker lists Ubuntu stonking as under investigation Ubuntu
Coverage2 articles · 2 outlets
One row per outlet, in order of first report. First in our coverage: SecurityOnline, 11 Nov.
- Wed 11 Nov, 19:00 UTC. SecurityOnline, first report. Node.js fixes HTTP/2 and TLS flaws exposing data and keys.
- Thu 12 Nov, 10:00 UTC. The Hacker News, its first report on the story. Node.js fixes 16 flaws exposing servers to crashes and data leaks.
- First report
- Article
- Running total
Show as tableHide table
| Published (UTC) | Outlet | Headline |
|---|---|---|
| 11 Nov 19:00 | SecurityOnline | Node.js fixes HTTP/2 and TLS flaws exposing data and keys |
| 12 Nov 10:00 | The Hacker News | Node.js fixes 16 flaws exposing servers to crashes and data leaks |
- Node.js fixes 16 flaws exposing servers to crashes and data leaksThe Hacker News · mentions it in passing
- Node.js fixes HTTP/2 and TLS flaws exposing data and keysSecurityOnline · first in our coverage · mentions it in passing
New articles also arrive in the RSS feed.