CyberSecBulletin
CVE-2025-59465NVD status: Modified

node: Uncontrolled Resource Consumption

Published Updated By the CyberSecBulletin desk

CVE-2025-59465 is a high-severity uncontrolled resource consumption vulnerability in node from Node.js, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.*, 5.*, 6.* as the first without the flaw, so updating node to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 3.96% chance of exploitation within 30 days, which is in the top 9.38% of all scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update node to 4.* or 5.* or 6.* or 7.*, whichever matches your release line, or a later version.
  2. Update Node.js to 20.20.0 or 22.22.0 or 24.13.0 or 25.3.0, whichever matches your release line, or a later version.
  3. Read the advisory on nodejs.org for workarounds and exact fixed builds.
  4. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Node.jsnode20.19.6 and earlier; 22.21.1 and earlier; 24.12.0 and earlier; 25.2.1 and earlier; 4.0 up to, but not including, 4.*; 5.0 up to, but not including, 5.*; 6.0 up to, but not including, 6.*; 7.0 up to, but not including, 7.*; and 11 more ranges4.*, 5.*, 6.*, 7.*, 8.*, 9.*
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10.0 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.4 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9.6 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Hardened ImagesNot specified in the recordNot stated
Node.jsNode.js20.0.0 up to, but not including, 20.20.0; 22.0.0 up to, but not including, 22.22.0; 24.0.0 up to, but not including, 24.13.0; 25.0.0 up to, but not including, 25.3.020.20.0, 22.22.0, 24.13.0, 25.3.0

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
NoneNothing can be modified.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by CNA.

Scoring systemScoreSeverityScored by
CVSS 3.17.5HighCNA
CVSS 3.07.5HighCNA (hackerone.com)

Official description

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) }) }) ```

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Uncontrolled Resource Consumption

The product does not properly control the allocation and maintenance of a limited resource.

How developers prevent this class of flaw

  • Ensure that protocols have specific limits of scale placed on them.
  • Ensure that all failures in resource allocation place the system into a safe posture.

More Uncontrolled Resource Consumption vulnerabilities (CWE-400)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in node

All node vulnerabilities

Recent Uncontrolled Resource Consumption vulnerabilities

Spotted an error? Tell us.