Home

Description

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 Reserved 2026-01-04 | Published 2026-03-30 | Updated 2026-03-31 | Assigner hackerone




MEDIUM: 5.3CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Product status

Default status
unaffected

20.20.1 (semver)
affected

22.22.1 (semver)
affected

24.14.0 (semver)
affected

25.8.1 (semver)
affected

References

nodejs.org/...log/vulnerability/march-2026-security-releases

cve.org (CVE-2026-21714)

nvd.nist.gov (CVE-2026-21714)

Download JSON