Skip to main content
CVE-2025-59465VulnerabilityPublished Updated

CVE-2025-59465: nodejs node · Vulnerability

Affects nodejs nodeSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.9% chance of exploitation in 30 days – higher than 90% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=20.19.6 <=20.19.6
  • >=22.21.1 <=22.21.1
  • >=24.12.0 <=24.12.0
  • >=25.2.1 <=25.2.1
  • =4.0
  • =5.0
  • =6.0
  • =7.0
  • =8.0
  • =9.0
  • =10.0
  • =11.0
  • =12.0
  • =13.0
  • =14.0
  • =15.0
  • =16.0
  • =17.0
  • =18.0
Fixed in–

AI-suggested

Red Hat has released security updates addressing CVE-2025-59465 in their Node.js packages. Applying these official patches is the recommended remediation. Users should update to the fixed versions provided by Red Hat as detailed in their advisories. Additionally, applications should implement explicit error handlers on secure sockets to prevent unhandled exceptions leading to crashes. Patch status is confirmed by Red Hat advisories; therefore, applying the vendor-provided updates is the primary mitigation.

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

References

Community reviews

Loading reviews…