CVE-2026-126051: Node.js is vulnerable to a remotely triggerable uncaught exception in TLS servers via deferred handshake callbacks

Published Nov 11, 2026
·
Updated

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.

Affected Software

2 affected componentsFixes available
Node.js Node.js>=26.0.0<26.13.1
26.13.1
Node.js Node.js>=24.0.0<24.22.3
24.22.3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 26.13.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 24.22.3

Event History

Nov 11, 2026
CVE Published
via Node.js·04:45 PM
Data Sourced
via Node.js·04:45 PM
SeverityAffected Software
CVE Published
via MITRE·06:35 PM
Data Sourced
via MITRE·06:35 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

Which deployments are exposed?

Node.js 26.x and 24.x TLS server deployments are affected when they use SNICallback, OCSPRequest, newSession, resumeSession, or server.addContext(). The issue is in TLS server handshake handling.

2

Does exploitation require authentication or interaction from a legitimate user?

No. A remote, unauthenticated attacker can trigger the condition during the TLS handshake, without user interaction.

3

What is the operational impact of a successful attempt?

The Node.js server process terminates due to an uncaught exception rather than emitting an error event. The reported impact is denial of service; no confidentiality or integrity impact is specified.

4

How can an operator identify potentially affected application configurations?

Review TLS server code for use of SNICallback, OCSPRequest, newSession, resumeSession, or server.addContext(). A server using one of these mechanisms on Node.js 26.x or 24.x is within the affected configuration described.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203