Skip to main content
CVE-2026-126051VulnerabilityPublished

Node.js TLS server handshake handling · Deferred-callback Use-after-destroy

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-126051· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade to 26.13.1 or 24.22.3 soon.

Data as of 11 Nov 2026, 22:34 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.07.5
Patch
Available – fixed in 26.13.1, 24.22.3
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade node to 26.13.1 or 24.22.3; node to 24.22.3.

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=25.0.0 <26.13.1
Fixed in
  • 26.13.1
nodejsnodeAffected
  • >=24.0.0 <24.22.3
Fixed in
  • 24.22.3
npmnodepkg:npm/nodeOther threatsAffected
  • <24.22.3 >=24.0.0
Fixed in
  • 24.22.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, consider mitigating by avoiding use of the affected TLS hooks or by implementing external process supervision to automatically restart the Node.js server if it crashes.

Description

A use-after-destroy vulnerability exists in Node.js TLS server handshake handling when using certain OpenSSL callbacks. This flaw allows a remote, unauthenticated attacker to cause the Node.js server process to terminate unexpectedly by sending a specially crafted client hello message followed by a socket FIN. The issue affects Node.js versions 24.x and 26.x and results in an uncaught exception that crashes the server process.

References

Community reviews

Loading reviews…