CVE Watchtower

CVE-2025-59465Nodejs Node.js Uncontrolled Resource Consumption

NVDCVSS scored by 0b0ca135-0b70-47e7-9f44-1890c2a1c46c

Vulnerability Summary

A 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)
})
})
```
Severity Level
HIGH(7.5)
Published Date
Jan 20, 2026
Last Modified
Jul 15, 2026
Exploitation Status
No confirmed exploitation yet
EPSS Score (30-Day)
3.62%Probability
Root Weakness (CWE)
The product does not properly control the allocation and maintenance of a limited resource, enabling denial-of-service conditions.
See the MITRE CWE entry for the full definition of this weakness.
CVSS v3.1 Base Metrics — Score 7.5 (HIGH)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionNone
ScopeUnchanged
ConfidentialityNone
IntegrityNone
AvailabilityHigh

Affected & Patched Versions

Affected Versions
  • Nodejs Node.js >= 20.0.0 and < 20.20.0
  • Nodejs Node.js >= 22.0.0 and < 22.22.0
  • Nodejs Node.js >= 24.0.0 and < 24.13.0
  • Nodejs Node.js >= 25.0.0 and < 25.3.0
  • nodejs node >= 20.19.6 and <= 20.19.6
  • nodejs node >= 22.21.1 and <= 22.21.1
  • nodejs node >= 24.12.0 and <= 24.12.0
  • nodejs node >= 25.2.1 and <= 25.2.1
  • nodejs node >= 4.0 and < 4.*
  • nodejs node >= 5.0 and < 5.*
  • nodejs node >= 6.0 and < 6.*
  • nodejs node >= 7.0 and < 7.*
  • nodejs node >= 8.0 and < 8.*
  • nodejs node >= 9.0 and < 9.*
  • nodejs node >= 10.0 and < 10.*
  • nodejs node >= 11.0 and < 11.*
  • nodejs node >= 12.0 and < 12.*
  • nodejs node >= 13.0 and < 13.*
  • nodejs node >= 14.0 and < 14.*
  • nodejs node >= 15.0 and < 15.*
  • nodejs node >= 16.0 and < 16.*
  • nodejs node >= 17.0 and < 17.*
  • nodejs node >= 18.0 and < 18.*
Patched Versions
  • Nodejs Node.js 20.20.0
  • Nodejs Node.js 22.22.0
  • Nodejs Node.js 24.13.0
  • Nodejs Node.js 25.3.0
  • nodejs node 20.19.6
  • nodejs node 22.21.1
  • nodejs node 24.12.0
  • nodejs node 25.2.1
  • nodejs node 4.*
  • nodejs node 5.*
  • nodejs node 6.*
  • nodejs node 7.*
  • nodejs node 8.*
  • nodejs node 9.*
  • nodejs node 10.*
  • nodejs node 11.*
  • nodejs node 12.*
  • nodejs node 13.*
  • nodejs node 14.*
  • nodejs node 15.*
  • nodejs node 16.*
  • nodejs node 17.*
  • nodejs node 18.*

What to do

Plan remediation soon. No exploitation is confirmed yet, but the severity is high.

  1. Check whether you run Nodejs Node.js and which version.
  2. Update to a patched version listed above, then confirm the new version.

Timeline

  • Jan 20, 2026Published
  • Jul 15, 2026Record last modified

Score, severity and exploitation changes are tracked from the day Watchtower started logging them.

Get notified about new Nodejs Node.js CVEsYou are reading CVE-2025-59465. Get an email when KEV listings, exploits or new CVEs match your stack.
Set up CVE alerts

Data last checked: Nov 22, 2026 14:11 UTC