Skip to main content
VulnerabilityPublished

CVE-2026-21714: nodejs node · Memory Leak

Affects nodejs nodeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=20.20.1 <=20.20.1
  • >=22.22.1 <=22.22.1
  • >=24.14.0 <=24.14.0
  • >=25.8.1 <=25.8.1
Fixed in–
npmnodepkg:npm/nodeOther threatsAffected
  • 20.20.1 – 25.8.1
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor the Node.js project advisories for updates. Until a fix is available, consider limiting exposure of HTTP/2 services or implementing resource monitoring and automated restarts to mitigate potential memory exhaustion. Avoid relying on generic mitigations not directly related to this specific memory leak.

Description

A memory leak vulnerability exists in Node.js HTTP/2 servers when clients send WINDOW_UPDATE frames on stream 0 that cause the flow control window to exceed the maximum allowed value. Although the server sends a GOAWAY frame correctly, the associated Http2Session object is not cleaned up, leading to resource leakage. This affects Node.js versions 20.20.1, 22.22.1, 24.14.

References

Community reviews

Loading reviews…