CVE-2025-23085

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.

Published: 2025-02-07 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-23085 is rated Low Risk (34.5/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-23085

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-25 0.14% 0.17% +0.03%
2 2026-03-21 0.16% 0.14% -0.02%
3 2026-03-04 — 0.16% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-23085

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.0 MEDIUM
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 3.9 1.4 [email protected]

Weakness enumeration for CVE-2025-23085

OS Trackers for CVE-2025-23085

vendor priority summary link
alpine medium CVE-2025-23085: 1 source package rows (nodejs); 3 state rows across 3 repos (3.21-main, 3.22-main, edge-main); fixed 3, open 0. https://security.alpinelinux.org/vuln/CVE-2025-23085
debian not yet assigned CVE-2025-23085 not yet assigned priority: Debian including 1 source packages (nodejs), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-23085
gentoo high CVE-2025-23085: 1 GLSA(s) (202506-08), 1 atom(s) (net-libs/nodejs); latest impact high. https://bugs.gentoo.org/buglist.cgi?quicksearch=CVE-2025-23085
redhat medium — https://access.redhat.com/security/cve/CVE-2025-23085
suse medium CVE-2025-23085 severity moderate: SUSE including 71 source package names (0.0.17-1.1:nodejs22-22.13.1-150600.13.6.1, 0.0.17-1.1:npm22-22.13.1-150600.13.6.1, …), 149 product×package rows across 27 product lines (Container bci/nodejs, Container containers/open-webui, … (27 product lines)): Fixed 132, Known Not Affected 17. https://www.suse.com/security/cve/CVE-2025-23085/
ubuntu medium CVE-2025-23085 medium priority: Ubuntu including 1 source packages (nodejs), 10 status rows across 10 suites (bionic, focal, jammy, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 4, needed 3, ignored 2, released 1. https://ubuntu.com/security/CVE-2025-23085

Affected software / configurations for CVE-2025-23085

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-23085

cvelogic Threat Intelligence