ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-59466

We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when is enabled.

Published Jan 20, 2026 · catalog updated Jan 21, 2026 · Node

Last checked Nov 7, 2026. A connected source was read within the last 7 days.

Check if you run it

No confirmed exploitation is on record for CVE-2025-59466. EPSS is 0.68%. Act only if a listed version of Node is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.

Same product and reporting

Severity
Medium5.9
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.68%
Remediation
Advisory link
Affected products
vendor nodejs Node 25.2.1 ≤25.2.1

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

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor nodejs Node 25.2.1 ≤25.2.125.2.1 ≤25.2.1

How to fix CVE-2025-59466

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-59466. EPSS is 0.68%. Act only if a listed version of Node is installed.

Which versions are affected?

Compare what you have installed with nodejs Node 25.2.1 ≤25.2.1 25.2.1 ≤25.2.1. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.68%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jan 20, 2026 · EUVD

    Detected

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

  2. Jan 21, 2026 · EUVD

    Updated

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

Sources

  • CVE.orgVulnerability recordCVE-2025-59466

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-59466

    30-day exploitation probability 0.68%

    first.org
  • EUVDVulnerability recordEUVD-2026-3339

    We have identified a bug in Node.js error handling where "Maximum call stack size exceeded" errors become uncatchable when is enabled. Instead of reaching , the process terminates, making the crash unrecoverable. Applications that rely on (v22, v20) or (v24, v22, v20) become vuln

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Nov 7, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.

  • FIRST EPSSNov 7, 2026
  • CVE.orgNov 4, 2026
  • EUVDNov 4, 2026