CVE-2025-23085

MEDIUM
5.3
CVSS Score
Published: February 7, 2025 at 07:09 AM UTC
Updated: June 17, 2026 at 08:51 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
Severity
MEDIUM5.3
Exploit prediction
EPSS 1%
SSVC
No known exploit

Description

A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY notification. Additionally, if an invalid header was detected by nghttp2, causing the connection to be terminated by the peer, the same leak was triggered. This flaw could lead to increased memory consumption and potential denial of service under certain conditions. This vulnerability affects HTTP/2 Server users on Node.js v18.x, v20.x, v22.x and v23.x.

Affected

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

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.619.0 ≤ v < 19.*20.0 ≤ v < 20.18.221.0 ≤ v < 21.*22.0 ≤ v < 22.13.123.0 ≤ v < 23.6.14.0 ≤ v < 4.*5.0 ≤ v < 5.*6.0 ≤ v < 6.*7.0 ≤ v < 7.*8.0 ≤ v < 8.*9.0 ≤ v < 9.*10.011.012.013.014.015.016.017.018.019.020.021.022.023.04.05.06.07.08.09.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.20.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 19.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 20.18.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 21.*, so it looks safe — our inference, not a vendor statement
Affected range stops below 22.13.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 23.6.1, 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, and no fixed version or vendor advisory is recorded against it.

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.3MEDIUMhackerone
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-401

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card