CVE-2026-10725
Crux Protocol\ \
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-10725 is a high-severity Data Amplification (CWE-409) vulnerability in Crux Protocol\. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SC-5 (Denial-of-service Protection) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-34964
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation can reject or limit decompression of data whose expansion ratio exceeds safe thresholds.
DoS protection limits the resource-exhaustion impact when a decompression bomb is processed.
Resource allocation controls bound memory/CPU consumption that a data-amplification attack would otherwise exhaust.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure-development practices include input-validation and resource-limit checks that prevent improper handling of compressed data.
Runtime monitoring of compute resources can detect exhaustion caused by decompression bombs.
Capacity planning and monitoring directly limits the availability impact of data-amplification attacks.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can uncover decompression-bomb vulnerabilities before release.
Redundancy helps availability but does not address the root cause of the weakness.
Monitoring can detect anomalous resource usage but does not prevent the weakness.
Secure development lifecycle includes input validation and resource-limit checks that mitigate data-amplification attacks.
Application security requirements can mandate limits on decompression size and ratio.
Secure architecture principles encourage defensive design against resource-exhaustion threats.