CVE-2025-59465

HIGH

7.5

CVSS Score

Published: January 20, 2026 at 08:41 PM UTC

Updated: July 15, 2026 at 02:17 AM UTC

1 product affected across 1 vendorNode.js

Using node by nodejs?

Get instant alerts when new vulnerabilities affect node - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.5

Exploit prediction

EPSS 4%

SSVC

No known exploit

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Node.js · Node.js

95%

10.0 ≤ v < 10.*11.0 ≤ v < 11.*12.0 ≤ v < 12.*13.0 ≤ v < 13.*14.0 ≤ v < 14.*15.0 ≤ v < 15.*16.0 ≤ v < 16.*17.0 ≤ v < 17.*18.0 ≤ v < 18.*20.0.0 ≤ v < 20.20.022.0.0 ≤ v < 22.22.024.0.0 ≤ v < 24.13.025.0.0 ≤ v < 25.3.04.0 ≤ v < 4.*5.0 ≤ v < 5.*6.0 ≤ v < 6.*7.0 ≤ v < 7.*8.0 ≤ v < 8.*9.0 ≤ v < 9.*10.0 11.0 12.0 13.0 14.0 15.0 16.0 17.0 18.0 20.19.6 22.21.1 24.12.0 25.2.1 4.0 5.0 6.0 7.0 8.0 9.0

Affected range stops below 10.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 11.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 12.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 13.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 14.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 15.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 16.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 17.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 18.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 20.20.0, so it looks safe — our inference, not a vendor statement

Affected range stops below 22.22.0, so it looks safe — our inference, not a vendor statement

Affected range stops below 24.13.0, so it looks safe — our inference, not a vendor statement

Affected range stops below 25.3.0, so it looks safe — our inference, not a vendor statement

Affected range stops below 4.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 5.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 6.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 7.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 8.*, so it looks safe — our inference, not a vendor statement

Affected range stops below 9.*, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

https://nodejs.org/en/blog/vulnerability/december-2025-security-releases