CVE-2025-23085
mediumpriority · track · 0EPSS 0.014 · 72 %ileDEEURUUSEPSS · scored 2026-10-26
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (77)
Products and version ranges known to be affected.
- IBM Business Automation Workflow V24.0.0-V24.0.1all versionscert_bundDEcpe:/a:ibm:business_automation_workflow:v24.0.0_-_v24.0.1
- Red Hat Enterprise Linux Developer Hub 1all versionscert_bundDEcpe:/o:redhat:enterprise_linux:developer_hub_1
advisories (3)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2025-0156Node.js: Mehrere SchwachstellenDeutsch2025-01-21csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Node.js ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen preiszugeben, einen Denial-of-Service-Zustand herbeizuführen oder nicht näher spezifizierte Angriffe zu starten.
- BIT-node-2025-230852025-02-11vendor · osvUS
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.
- BIT-node-min-2025-230852025-02-11vendor · osvUS
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.
also known as (6)
Other names and identifiers for this entity.
- CNNVD-202502-597cnnvd
- EUVD-2025-3113enisa_euvd
- BDU:2025-02664fstec_bdu
- GHSA-qv9x-c8c9-rpr8enisa_euvd
- BIT-node-2025-23085osv
- BIT-node-min-2025-23085osv
sources
Which sources assert this record, and when.
references (7)
External citations — patches, advisories, analysis.
- https://nodejs.org/en/blog/vulnerability/january-2025-security-releasescnnvd
- https://vigilance.fr/vulnerability/Node-js-Core-three-vulnerabilities-dated-21-01-2025-46144cnnvd
- https://www.oracle.com/security-alerts/cpujul2025.htmlcnnvd
- https://nodejs.org/en/blog/vulnerability/january-2025-security-releasesenisa_euvd
- https://lists.debian.org/debian-lts-announce/2025/02/msg00031.htmlnvd
- https://nodejs.org/en/blog/vulnerability/january-2025-security-releasesnvd
- https://security.netapp.com/advisory/ntap-20250321-0003/nvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan