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.
Published: 2026-09-07
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

Protocol‑HTTP2 versions before 1.14 for Perl allow an attacker to exhaust server memory by repeatedly opening and closing HTTP/2 streams. When a stream enters the CLOSED state the module clears most of the stream’s keys but retains the entry in the connection stream table. Because stream identifiers strictly increase, each closed stream leaves a residual table entry that persists for the lifetime of the connection, allowing an attacker to accumulate tens of thousands of entries and grow memory usage linearly, as measured at roughly 920 bytes per closed stream.

Affected Systems

This vulnerability affects the Perl module Protocol::HTTP2, any version earlier than 1.14. Deployments using this module to handle HTTP/2 connections, whether as a server or client, are susceptible.

Risk and Exploitability

The lack of a reported EPSS score and absence from the CISA KEV catalogue suggest that the exploitation likelihood is not currently quantifiable, but the vulnerability can be leveraged remotely over the network by an attacker who can send many HTTP/2 streams to a target server. The impact is high memory consumption that could bring a service down, but successful exploitation requires sustained traffic and a vulnerable server configuration. No CVSS score is provided, so severity must be judged on the potential for denial of service and resource exhaustion.

Generated by OpenCVE AI on September 7, 2026 at 20:20 UTC.

Remediation

Vendor Solution

Upgrade to Protocol-HTTP2 1.14 or later.


Vendor Workaround

For deployments that are not able to upgrade to Protocol-HTTP2 1.14, close each connection after a fixed number of requests, which discards its stream table.


OpenCVE Recommended Actions

  • Upgrade to Protocol-HTTP2 1.14 or later.
  • If upgrade cannot be performed, close each connection after a fixed number of requests to discard its stream table.
  • Monitor server memory and application logs for anomalous growth and consider restarting or scaling the service if necessary.

Generated by OpenCVE AI on September 7, 2026 at 20:20 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 07 Sep 2026 19:00:00 +0000

Type Values Removed Values Added
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.
Title Protocol::HTTP2 versions before 1.14 for Perl allow memory exhaustion via closed streams that stream_state never removes from the connection stream table
Weaknesses CWE-401
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: CPANSec

Published:

Updated: 2026-09-07T20:07:29.934Z

Reserved: 2026-07-17T08:26:33.147Z

Link: CVE-2026-16028

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-09-07T19:17:25.927

Modified: 2026-09-07T19:17:25.927

Link: CVE-2026-16028

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-07T20:30:16Z

Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime