Skip to main content
CVE-2025-59466VulnerabilityPublished

CVE-2025-59466: nodejs node · Vulnerability

Affects nodejs nodeSource CVE Database V5

0

Not known to be exploited · CVSS 5.9 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score
5.9High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 52% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=20.19.6 <=20.19.6
  • >=22.21.1 <=22.21.1
  • >=24.12.0 <=24.12.0
  • >=25.2.1 <=25.2.1
  • =8.0
  • =9.0
  • =10.0
  • =11.0
  • =12.0
  • =13.0
  • =14.0
  • =15.0
  • =16.0
  • =17.0
  • =18.0
Fixed in–
npmnodepkg:npm/nodeOther threatsAffected
  • =8.0
  • =9.0
  • =10.0
  • =11.0
  • =12.0
  • =13.0
  • =14.0
  • =15.0
  • =16.0
  • =17.0
  • =18.0
  • =20.19.6
  • =22.21.1
  • =24.12.0
  • =25.2.1
Fixed in–

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

AI-suggested

1. Upgrade Node.js to the latest patched versions once official fixes are released by the Node.js project. Monitor Node.js security advisories for patch availability. 2. Until patches are available, audit and limit the use of async_hooks.createHook() and AsyncLocalStorage in applications, especially in code paths that may involve deep recursion or unbounded call stacks. 3. Implement application-level recursion depth checks or stack size monitoring to prevent triggering the vulnerability. 4. Use process monitoring and automated restarts to minimize downtime in case of crashes. 5. Employ defensive coding practices to avoid unbounded recursion and validate inputs that could cause stack overflows. 6. Consider isolating critical services using containerization or microservice architectures to limit the blast radius of crashes. 7. Review and enhance logging and alerting around process crashes to enable rapid detection and response. 8. Engage with Node.js community and security channels for updates and best practices related to async_hooks usage.

Description

We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when `async_hooks.createHook()` is enabled. Instead of reaching `process.on('uncaughtException')`, the process terminates, making the crash unrecoverable. Applications that rely on `AsyncLocalStorage` (v22, v20) or `async_hooks.createHook()` (v24, v22, v20) become vulnerable to denial-of-service crashes triggered by deep recursion under specific conditions.

References

Community reviews

Loading reviews…