# CVE-2026-116134: HTTP::Body versions before 1.23_01 for Perl allow memory exhaustion via an unbounded multipart part header block


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116134, GHSA-hm6g-hrhc-g7hv

## What is CVE-2026-116134?

CVE-2026-116134 is a vulnerability, published on 28 Oct 2026. 

### Official description

HTTP::Body versions before 1.23_01 for Perl allow memory exhaustion via an unbounded multipart part header block.

The multipart parser takes everything up to the first blank line after a boundary as the part's header block, with no limit on its size or number of lines. Every line is stored in the part's header hash, so a block of short lines costs about 60 bytes of memory per input byte.

A remote attacker can exhaust worker memory with a single request.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

No fix has been published for CVE-2026-116134 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116134 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116134 is a vulnerability, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116134 in the wild and no public exploit code.

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-116134/ (Markdown: https://insights.sbomify.com/CVE-2026-116134/index.md)
```

## Sources

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

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