high CVSS 7.5

CVE-2025-59466·Node.js vulnerability

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.

Severity
high
Software
Node.js
Fixed in
25.3.0
Published
2026-01-20

Affected versions

From: 25.0.0

Until: 25.3.0

Fixed in: 25.3.0

How to fix this CVE

Update Node.js to version 25.3.0 or later to resolve the uncatchable stack overflow vulnerability in async_hooks. Applications using AsyncLocalStorage or async_hooks.createHook() should prioritize this update, as the vulnerability can cause unrecoverable process crashes during deep recursion scenarios. Test the patched version in a staging environment before deploying to production.

sudo dnf update nodejs

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed Node.js version: node --version or nodejs --version
  2. Verify if async_hooks or AsyncLocalStorage are in use: grep -r 'async_hooks\|AsyncLocalStorage' /path/to/application/src --include='*.js'
  3. Search application logs for 'Maximum call stack size exceeded' followed by process termination without uncaughtException handler output: grep -i 'maximum call stack' /var/log/application.log
  4. Confirm patch installation by running node --version and verifying output is 25.3.0 or later

FAQ

What is CVE-2025-59466?

CVE-2025-59466 is a denial-of-service vulnerability in Node.js where stack overflow errors bypass the uncaughtException handler when async_hooks are enabled, causing the process to crash unrecoverably instead of being caught by error handlers.

Is CVE-2025-59466 being actively exploited?

No, CVE-2025-59466 is not listed on the CISA Known Exploited Vulnerabilities catalog and no public exploits have been disclosed.

What versions of Node.js are affected by CVE-2025-59466?

Node.js versions 25.0.0 through 25.2.0 are vulnerable. Version 25.3.0 and later contain the fix.

How do I check if my server is vulnerable to CVE-2025-59466?

Run `node --version` and confirm the version is between 25.0.0 and 25.2.0. Then check if your application imports async_hooks or AsyncLocalStorage with `grep -r 'require.*async_hooks\|from.*async_hooks\|AsyncLocalStorage' /path/to/app`.

Does Defensia detect CVE-2025-59466?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Node.js is installed on a monitored server, CVE-2025-59466 will appear in your dashboard with remediation steps.

Related Node.js CVEs

CVE-2026-21636CVSS 10A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when `--permission` is enabled. Even without `--allow-net`, attacker-controlled inputs (such as URLs or socketPath options) can connect to arbitrary local sockets via net, tls, or undici/fetch. This breaks the intended security boundary of the permission model and enables access to privileged local services, potentially leading to privilege escalation, data exposure, or local code execution. * The issue affects users of the Node.js permission model on version v25. In the moment of this vulnerability, network permissions (`--allow-net`) are still in the experimental phase.
CVE-2025-55130CVSS 9.1A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.
CVE-2025-59464CVSS 7.5A memory leak in Node.js’s OpenSSL integration occurs when converting `X.509` certificate fields to UTF-8 without freeing the allocated buffer. When applications call `socket.getPeerCertificate(true)`, each certificate field leaks memory, allowing remote clients to trigger steady memory growth through repeated TLS connections. Over time this can lead to resource exhaustion and denial of service.
CVE-2025-59465CVSS 7.5A malformed `HTTP/2 HEADERS` frame with oversized, invalid `HPACK` data can cause Node.js to crash by triggering an unhandled `TLSSocket` error `ECONNRESET`. Instead of safely closing the connection, the process crashes, enabling a remote denial of service. This primarily affects applications that do not attach explicit error handlers to secure sockets, for example: ``` server.on('secureConnection', socket => { socket.on('error', err => { console.log(err) }) }) ```
CVE-2026-21637CVSS 7.5A flaw in Node.js TLS error handling allows remote attackers to crash or exhaust resources of a TLS server when `pskCallback` or `ALPNCallback` are in use. Synchronous exceptions thrown during these callbacks bypass standard TLS error handling paths (tlsClientError and error), causing either immediate process termination or silent file descriptor leaks that eventually lead to denial of service. Because these callbacks process attacker-controlled input during the TLS handshake, a remote client can repeatedly trigger the issue. This vulnerability affects TLS servers using PSK or ALPN callbacks across Node.js versions where these callbacks throw without being safely wrapped.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-59466. Free for 1 server.

Get started free