CVE-2025-23085: NodeJS vulnerability
NodeJS · Node
Vendor fix available · Affected: NodeJS · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 72% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- NodeJS · Nodefrom 4.0 before 4.*; from 5.0 before 5.*; from 6.0 before 6.*; from 7.0 before 7.*; from 8.0 before 8.*; from 9.0 before 9.* and 14 more
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- NodeJS
- Published
- February 2025
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2025-23085
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- GOAWAY HTTP/2 frames cause memory leak outside heapNode.js · 2025 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2025-23085 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.