node · Vulnerability
cve-program · CVE-2026-126051
PublishedA 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.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2026-126051 · CVE overview and exploitation status
cve-program · CVE-2026-126051
Related changes
Linked by CVE identifier- Node.js is vulnerable to a remotely triggerable uncaught exception in TLS servers via deferred handshake callbacks · Newly collected advisory · 11 Nov 2026
- Wednesday, November 11, 2026 Security Releases · Security advisory · 11 Nov 2026