CVE-2026-10725: CWE-409 Improper Handling of Highly Compressed Data (Data Amplification) in CRUX Protocol::HTTP2
Protocol::HTTP2 versions through 1. 12 for Perl contain a vulnerability where the HTTP/2 inbound HPACK header decoding does not enforce the advertised MAX_HEADER_LIST_SIZE limit. This allows a small HTTP/2 request to expand into a large memory allocation on the server, creating a potential denial-of-service condition known as an HTTP/2 bomb. The vulnerability arises because the headers_decode method copies full key-value pairs without size checks, and the stream_header_block_add method appends CONTINUATION frames without bounds. No official patch or remediation guidance is currently available.
AI Analysis
Technical Summary
The Protocol::HTTP2 Perl module up to version 1.12 is vulnerable to a memory amplification attack due to improper handling of highly compressed HTTP/2 header data. Specifically, the inbound HPACK decoder does not enforce the MAX_HEADER_LIST_SIZE limit advertised in SETTINGS frames, allowing attackers to send small requests that expand into large memory usage on the server. The headers_decode method materializes full copies of header key-value pairs without size checks, and the stream_header_block_add method appends CONTINUATION frames without limits. This results in unbounded memory consumption, classified under CWE-409 (Improper Handling of Highly Compressed Data). No patch or official remediation has been documented.
Potential Impact
An attacker can exploit this vulnerability to cause excessive memory consumption on servers using Protocol::HTTP2 versions through 1.12, potentially leading to denial of service by exhausting server memory resources. There are no known exploits in the wild at this time. The vulnerability does not indicate direct code execution or data leakage but impacts availability through resource exhaustion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider mitigating exposure by limiting or filtering HTTP/2 traffic to affected servers or disabling HTTP/2 support in Protocol::HTTP2 if feasible. Monitoring for unusually large header blocks may help detect exploitation attempts, but no vendor-provided mitigation or temporary fix is currently documented.
CVE-2026-10725: CWE-409 Improper Handling of Highly Compressed Data (Data Amplification) in CRUX Protocol::HTTP2
Description
Protocol::HTTP2 versions through 1. 12 for Perl contain a vulnerability where the HTTP/2 inbound HPACK header decoding does not enforce the advertised MAX_HEADER_LIST_SIZE limit. This allows a small HTTP/2 request to expand into a large memory allocation on the server, creating a potential denial-of-service condition known as an HTTP/2 bomb. The vulnerability arises because the headers_decode method copies full key-value pairs without size checks, and the stream_header_block_add method appends CONTINUATION frames without bounds. No official patch or remediation guidance is currently available.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Protocol::HTTP2 Perl module up to version 1.12 is vulnerable to a memory amplification attack due to improper handling of highly compressed HTTP/2 header data. Specifically, the inbound HPACK decoder does not enforce the MAX_HEADER_LIST_SIZE limit advertised in SETTINGS frames, allowing attackers to send small requests that expand into large memory usage on the server. The headers_decode method materializes full copies of header key-value pairs without size checks, and the stream_header_block_add method appends CONTINUATION frames without limits. This results in unbounded memory consumption, classified under CWE-409 (Improper Handling of Highly Compressed Data). No patch or official remediation has been documented.
Potential Impact
An attacker can exploit this vulnerability to cause excessive memory consumption on servers using Protocol::HTTP2 versions through 1.12, potentially leading to denial of service by exhausting server memory resources. There are no known exploits in the wild at this time. The vulnerability does not indicate direct code execution or data leakage but impacts availability through resource exhaustion.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider mitigating exposure by limiting or filtering HTTP/2 traffic to affected servers or disabling HTTP/2 support in Protocol::HTTP2 if feasible. Monitoring for unusually large header blocks may help detect exploitation attempts, but no vendor-provided mitigation or temporary fix is currently documented.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-06-03T09:18:37.572Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a23f084e29bf47b504c29e2
Added to database: 6/6/2026, 10:03:48 AM
Last enriched: 6/6/2026, 10:18:32 AM
Last updated: 6/6/2026, 11:17:38 AM
Views: 12
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.