CVE-2026-21714

A memory leak occurs in Node.js HTTP/2 servers when a client sends WINDOW_UPDATE frames on stream 0 (connection-level) that cause the flow control window to exceed the maximum value of 2³¹-1. The server correctly sends a GOAWAY frame, but the Http2Session object is never cleaned up. This vulnerability affects HTTP2 users on Node.js 20, 22, 24 and 25.

Published: 2026-03-30 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]
NVD Status：Awaiting Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-21714 is rated Low Risk (34.2/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.45%). 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-2026-21714

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-06-15 0.01% 0.45% +0.44%
2 2026-03-31 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-21714

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-2026-21714

OS Trackers for CVE-2026-21714

vendor priority summary link
alpine — CVE-2026-21714: 1 source package rows (nodejs); 4 state rows across 4 repos (3.21-main, 3.22-main, 3.23-main, edge-main); fixed 4, open 0. https://security.alpinelinux.org/vuln/CVE-2026-21714
debian not yet assigned CVE-2026-21714 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-2026-21714
redhat medium — https://access.redhat.com/security/cve/CVE-2026-21714
suse medium CVE-2026-21714 severity moderate: SUSE including 66 source package names (corepack24-24.14.1-1.1, corepack24-24.14.1-160000.1.1, …), 137 product×package rows across 20 product lines (SUSE Liberty Linux 8, SUSE Liberty Linux 9, … (20 product lines)): Known Not Affected 79, Fixed 53, First Fixed 5. https://www.suse.com/security/cve/CVE-2026-21714/
ubuntu medium CVE-2026-21714 medium priority: Ubuntu including 1 source packages (nodejs), 8 status rows across 8 suites (bionic, focal, jammy, noble, questing, trusty, upstream, xenial): needs-triage 7, released 1. https://ubuntu.com/security/CVE-2026-21714

Affected software / configurations for CVE-2026-21714

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-21714

cvelogic Threat Intelligence