CVE-2026-21714: nodejs vulnerability
nodejs · node
Affected: nodejs · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 37% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- nodejs · nodefrom 20.20.1 up to and including 20.20.1; from 22.22.1 up to and including 22.22.1; from 24.14.0 up to and including 24.14.0; from 25.8.1 up to and including 25.8.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- nodejs
- Published
- March 2026
- Bounty reports
- 1 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2026-21714
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- Memory leak in Node.js HTTP/2 server via WINDOW_UPDATE on stream 0 leads to resource exhaustionNode.js · 2026 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2026-21714 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.