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: 7.5 High
EPSS: < 1% Very Low
KEV: No
Impact: Memory Exhaustion (Denial of Service)
Action: Patch
AI Analysis

Impact

Protocol::HTTP2 versions before 1.14 for Perl have a flaw where closed streams are retained in the connection stream table, causing a memory leak. When an HTTP/2 stream ends, the module clears most of the stream’s data but does not remove the entry, so each subsequent closed stream keeps a small residual allocation. An attacker can repeatedly open and close streams over a long‑lived connection, causing the server’s memory usage to grow linearly and potentially exhaust available memory, leading to denial of service.

Affected Systems

Any deployment of the Perl module Protocol::HTTP2 that processes HTTP/2 connections and uses a version earlier than 1.14 is affected. The issue is present in releases such as 1.13 and earlier.

Risk and Exploitability

The CVSS score of 7.5 indicates a high severity for a remote memory‑exhaustion vulnerability. The EPSS score of < 1 % suggests that exploitation is currently unlikely, and the CVE is not listed in the CISA KEV catalog. The likely attack vector involves a remote attacker establishing a long‑lived HTTP/2 connection to the vulnerable server and repeatedly creating and closing streams; each cycle leaves a residual table entry that increases the server’s resident memory. Successful exploitation would require sustained traffic, but if achieved it could push the server to run out of memory or force a restart, thereby denying service to legitimate users.

Generated by OpenCVE AI on September 10, 2026 at 05:08 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 newer.
  • If the upgrade cannot be performed, configure the application to close each TCP connection after a fixed number of requests; this discards the connection stream table and prevents continuous growth.
  • Monitor server memory consumption and application logs for abnormal growth; consider restarting or scaling the service when memory thresholds are approached.

Generated by OpenCVE AI on September 10, 2026 at 05:08 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 08 Sep 2026 19:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Mon, 07 Sep 2026 21:30:00 +0000

Type Values Removed Values Added
References

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-08T18:39:40.768Z

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

Link: CVE-2026-16028

cve-icon Vulnrichment

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

cve-icon NVD

Status : Deferred

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

Modified: 2026-09-08T19:17:50.877

Link: CVE-2026-16028

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-10T05:15:17Z

Weaknesses
  • CWE-401

    Missing Release of Memory after Effective Lifetime