CVE-2025-59466: nodejs vulnerability
nodejs · node
Vendor fix available · Affected: nodejs · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 53% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- nodejs · nodefrom 20.19.6 up to and including 20.19.6; from 22.21.1 up to and including 22.21.1; from 24.12.0 up to and including 24.12.0; from 25.2.1 up to and including 25.2.1; from 8.0 before 8.*; from 9.0 before 9.* and 9 more
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- nodejs
- Published
- January 2026
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2025-59466
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- Uncatchable "Maximum call stack size exceeded" error on Node.js via async_hooks leads to process crashes bypassing error handlersNode.js · 2026 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2025-59466 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.