CVE-2026-16028 Details
Description
Protocol::HTTP2 versions before 1.14 for Perl allow memory exhaustion via closed streams that stream_state never removes from the connection stream table. When a stream reaches the CLOSED state, stream_state returns the concurrency slot and clears most of the stream's keys, but the entry itself stays in the connection stream table and nothing in the distribution removes it. Stream identifiers increase monotonically, so a peer can open and close streams on one connection indefinitely, each close leaving a residual entry that is retained for the life of the connection. SETTINGS_MAX_CONCURRENT_STREAMS does not bound this. That setting caps how many streams are live at once and is enforced, while the growth is made of streams the cap has already released, so it accumulates with concurrency never exceeding one. The client keeps the same table and grows the same way against a hostile server. Measured against a server built on this module, roughly 920 bytes are retained per closed stream for about 19 bytes on the wire, so 100,000 sequential streams on one connection grow server resident memory by about 88 MiB. The streams are ordinary requests that the application accepts and completes.
A memory exhaustion vulnerability has been identified in Protocol::HTTP2 versions prior to 1.14 for Perl. This issue arises from closed streams that the stream_state component fails to remove from the connection stream table, leading to residual entries that accumulate and are retained for the life of the connection. When a stream is closed, stream_state clears most of its keys but leaves the entry in the connection stream table. As stream identifiers increase monotonically, a peer can indefinitely open and close streams on a single connection, with each closure leaving a residual entry. This vulnerability is not mitigated by the SETTINGS_MAX_CONCURRENT_STREAMS setting, which only caps the number of active streams at once. Instead, the issue exploits the growth of closed streams, which can lead to significant memory retention on the server side. For instance, approximately 920 bytes are held per closed stream, while only about 19 bytes are transmitted over the wire. Consequently, closing 100,000 sequential streams on one connection can increase server-resident memory usage by around 88 MiB.
Users are advised to upgrade to Protocol::HTTP2 version 1.14 or later. For those unable to upgrade, a temporary workaround is to close each connection after a fixed number of requests, which will discard the stream table and mitigate the memory exhaustion effect.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Sep 7, 2026CISA-ADP
Assessed Sep 8, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/vlet/p5-Protocol-HTTP2/commit/27a488a34d74fd16f123e5e6186d4f677faa246f.patch | CPANSec | Source CodeVendor |
| https://metacpan.org/release/CRUX/Protocol-HTTP2-1.13/source/lib/Protocol/HTTP2/Stream.pm#L113-126 | CPANSec | Source CodeVendor |
| https://metacpan.org/release/CRUX/Protocol-HTTP2-1.14/changes | CPANSec | Release NotesVendor |
| http://www.openwall.com/lists/oss-security/2026/09/07/2 | CVE | AdvisoryMailing ListRemedy |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-401 | Missing Release of Memory after Effective Lifetime | CPANSec |
Affected Products
| Product | Versions |
|---|---|
| Protocol::HTTP2 | < 1.14 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Sep 8, 2026 | CVE Modified | CISA-ADP |
| Sep 7, 2026 | CVE Modified | CVE |
| Sep 7, 2026 | New CVE Received | CPANSec |
Volerion