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.
CVE-2026-21714
MEDIUMPre-NVD 5.35.3—Trending — 4 sources updated this week
EchelonGraph scoreMEDIUM confidence
Score 5.3 from GitHub Security Advisory published 2026-03-30. the CNA's CVSS baseline 5.3; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: cna:hackerone, ghsa
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0
A fix is available — apply it.
- CVSS v3
- 5.3
- EG Score
- 5.3(medium)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability100% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
March 30, 2026
Last Modified
June 17, 2026
References (1)
Vendor Advisories for CVE-2026-21714(4)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- CVE-2026-21714Microsoft Security Response Center (MSRC)Medium
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.
- RHSA-2026:7670Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security update
- RHSA-2026:7675Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs24 security update
- RHSA-2026:7350Red Hat Product SecurityHigh
Red Hat Security Advisory: nodejs:24 security update
Patch Availability(3)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | nodejs24-1:24.14.1-2.el10_1 | 2026-04-13 | redhat |
| redhat | nodejs:24-8100020260408131901.6d880403 | 2026-04-13 | redhat |
| redhat | nodejs:24-9070020260402152654.rhel9 | 2026-04-09 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCVendor advisory
- 2026-07-27 12:50 UTCGHSA enrichment
Frequently asked(5)
What is CVE-2026-21714?
CVE-2026-21714 is a medium vulnerability published on March 30, 2026. 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…
When was CVE-2026-21714 disclosed?
CVE-2026-21714 was first published in the National Vulnerability Database on March 30, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-21714 actively exploited?
CVE-2026-21714 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 63.0% of all scored CVEs.
What is the CVSS score of CVE-2026-21714?
CVE-2026-21714 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-21714?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-21714, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-21714
Is Your Infrastructure Affected by CVE-2026-21714?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.