CVE-2025-23085: A memory leak could occur when a remote peer abruptly closes the socket without sending a GOAWAY
Source GCVE Database
Not known to be exploited · CVSS 5.3 Medium · fixed in 24.0.0 : update affected systems when convenient.
Data as of 30 Oct 2026, 01:10 UTC
Thin evidence
One scorer or none| CNA (hackerone) | CVSS 3.0 | 5.3 |
|---|
- Patch
- Available – fixed in 24.0.0, 23.0.0, 21.0.0 +1
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 7 Feb 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 29 Oct 2026.
What to do
AI-suggested
If you cannot patch yet, monitoring for abnormal memory usage and limiting exposure to untrusted HTTP/2 clients may reduce risk.
Description
A memory leak vulnerability exists in the HTTP/2 server implementation of Node.js versions 18.x, 20.x, 22.x, and 23.x. The leak occurs when a remote peer abruptly closes the socket without sending a GOAWAY notification or when an invalid header causes the connection to be terminated by the peer. This flaw can lead to increased memory consumption and potential denial of service under certain conditions.