CVE-2026-10725: CWE-409 Improper Handling of Highly Compressed Data (Data Amplification) in CRUX Protocol::HTTP2
Protocol::HTTP2 versions before 1.13 for Perl is vulnerable to a HTTP/2 Bomb. Protocol::HTTP2's inbound HPACK path has no header-list size limit, so a small HTTP/2 request can expand into large server memory (the "HTTP/2 bomb"). The headers_decode method materialises a full key+value copy per indexed reference with no running size check, and the stream_header_block_add method appends (since version 1.12) every CONTINUATION frame to the per-stream buffer unbounded. MAX_HEADER_LIST_SIZE (default 65536) is advertised in SETTINGS but never consulted on decode. It is absent from the decoder and from the :limits export tag.
AI Analysis
Technical Summary
The Protocol::HTTP2 Perl module prior to version 1.13 is vulnerable to a denial-of-service condition due to improper handling of highly compressed HTTP/2 headers (CWE-409). Specifically, the inbound HPACK decoding path does not enforce the MAX_HEADER_LIST_SIZE limit advertised in SETTINGS, allowing an attacker to send a small request that expands into a large memory allocation (the HTTP/2 bomb). The headers_decode method creates full copies of keys and values for indexed references without size checks, and from version 1.12, the stream_header_block_add method appends every CONTINUATION frame to the per-stream buffer without bounds. This unbounded memory consumption can lead to resource exhaustion and service disruption.
Potential Impact
This vulnerability can be exploited remotely without authentication (AV:N/AC:L/PR:N/UI:N) to cause a denial of service by exhausting server memory (Availability impact: High). There is no impact on confidentiality or integrity. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a fix is available, consider limiting or filtering HTTP/2 traffic from untrusted sources or applying external protections to mitigate potential memory exhaustion attacks.
CVE-2026-10725: CWE-409 Improper Handling of Highly Compressed Data (Data Amplification) in CRUX Protocol::HTTP2
Description
Protocol::HTTP2 versions before 1.13 for Perl is vulnerable to a HTTP/2 Bomb. Protocol::HTTP2's inbound HPACK path has no header-list size limit, so a small HTTP/2 request can expand into large server memory (the "HTTP/2 bomb"). The headers_decode method materialises a full key+value copy per indexed reference with no running size check, and the stream_header_block_add method appends (since version 1.12) every CONTINUATION frame to the per-stream buffer unbounded. MAX_HEADER_LIST_SIZE (default 65536) is advertised in SETTINGS but never consulted on decode. It is absent from the decoder and from the :limits export tag.
CVSS v3.1
Score 7.5high
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Protocol::HTTP2 Perl module prior to version 1.13 is vulnerable to a denial-of-service condition due to improper handling of highly compressed HTTP/2 headers (CWE-409). Specifically, the inbound HPACK decoding path does not enforce the MAX_HEADER_LIST_SIZE limit advertised in SETTINGS, allowing an attacker to send a small request that expands into a large memory allocation (the HTTP/2 bomb). The headers_decode method creates full copies of keys and values for indexed references without size checks, and from version 1.12, the stream_header_block_add method appends every CONTINUATION frame to the per-stream buffer without bounds. This unbounded memory consumption can lead to resource exhaustion and service disruption.
Potential Impact
This vulnerability can be exploited remotely without authentication (AV:N/AC:L/PR:N/UI:N) to cause a denial of service by exhausting server memory (Availability impact: High). There is no impact on confidentiality or integrity. No known exploits are reported in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or patch is currently documented. Until a fix is available, consider limiting or filtering HTTP/2 traffic from untrusted sources or applying external protections to mitigate potential memory exhaustion attacks.
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: 06/06/2026, 10:03:48 UTC
Last enriched: 06/14/2026, 09:34:03 UTC
Last updated: 07/31/2026, 19:22:57 UTC
Views: 126
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.