PublishedCVE-2025-23085·
5.3Medium
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 10.*, 11.*, 12.* and 17 more.
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.
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| nodejs | >=10.0 <10.*, >=11.0 <11.*, >=12.0 <12.*, >=13.0 <13.*, >=14.0 <14.*, >=15.0 <15.*, >=16.0 <16.*, >=17.0 <17.*, >=18.0 <18.20.6, >=19.0 <19.*, >=20.0 <20.18.2, >=21.0 <21.*, >=22.0 <22.13.1, >=23.0 <23.6.1, >=4.0 <4.*, >=5.0 <5.*, >=6.0 <6.*, >=7.0 <7.*, >=8.0 <8.*, >=9.0 <9.* | 10.*, 11.*, 12.*, 13.*, 14.*, 15.*, 16.*, 17.*, 18.20.6, 19.*, 20.18.2, 21.*, 22.13.1, 23.6.1, 4.*, 5.*, 6.*, 7.*, 8.*, 9.* |
Every event on this vulnerability
A live severity badge for an advisory, README or ticket