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.
No configuration.
03 Nov 2025, 21:19
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
25 Feb 2025, 13:15
| Type | Values Removed | Values Added |
|---|---|---|
| References |
|
|
| Summary |
|
07 Feb 2025, 16:15
| Type | Values Removed | Values Added |
|---|---|---|
| CWE | CWE-401 |
07 Feb 2025, 07:15
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Published : 2025-02-07 07:15
Updated : 2025-11-03 21:19
NVD link : CVE-2025-23085
Mitre link : CVE-2025-23085
CVE.ORG link : CVE-2025-23085
JSON object : View
No product.
Missing Release of Memory after Effective Lifetime