# CVE-2026-10725: Protocol::HTTP2 versions before 1.13 for Perl is vulnerable to a HTTP/2 Bomb

> A remote attacker can cause denial of service by sending small HTTP/2 requests that expand into large memory usage due to missing header size limits.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jun 2026
- **Updated:** 9 Jun 2026
- **Also known as:** DEBIAN-CVE-2026-10725, GHSA-q432-rmqv-hh8m, SUSE-SU-2026:22188-1, SUSE-SU-2026:2306-1, UBUNTU-CVE-2026-10725, openSUSE-SU-2026:10988-1, openSUSE-SU-2026:21125-1

## What is CVE-2026-10725?

CVE-2026-10725 is a high-severity denial of service vulnerability in CRUX Protocol::HTTP2, published on 6 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-409 (Improper Handling of Highly Compressed Data (Data Amplification))

## Which versions are affected by CVE-2026-10725?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-Protocol-HTTP2` | SUSE:Linux Enterprise Server 16.0 | All versions | 1.10-160000.3.1 |
| `perl-Protocol-HTTP2` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 1.10-160000.3.1 |
| `perl-Protocol-HTTP2` | openSUSE:Leap 16.0 | All versions | 1.10-160000.3.1 |
| `perl-Protocol-HTTP2` | openSUSE:Tumbleweed | All versions | 1.130.0-1.1 |

Products: Crux Protocol\.

## How do I fix CVE-2026-10725?

Upgrade to a fixed version.

## Is CVE-2026-10725 being exploited?

There is no known exploitation of CVE-2026-10725 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10725 and fix it if it is affected.

What it is: CVE-2026-10725 is a high-severity denial of service vulnerability in CRUX Protocol::HTTP2, published on 6 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-10725 in the wild and no public exploit code.

Affected product: CRUX Protocol::HTTP2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10725/ (Markdown: https://insights.sbomify.com/CVE-2026-10725/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10725
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10725
- OSV: https://osv.dev/vulnerability/CVE-2026-10725

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10725/
Summaries are generated and may contain mistakes; the official description above is the record.