# CVE-2026-121006: HTTP::Body versions before 1.24_02 for Perl parse the trailer in quadratic time


- **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
- **Fix available:** Yes
- **Published:** 6 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** DEBIAN-CVE-2026-121006, DHI-u6th-b6xl-enzp-bvmd, GHSA-f4c2-m2fq-wp7w, UBUNTU-CVE-2026-121006

## What is CVE-2026-121006?

CVE-2026-121006 is a high-severity vulnerability, published on 6 Nov 2026. 

### Official description

HTTP::Body versions before 1.24_02 for Perl parse the trailer in quadratic time.

Everything after the last chunk in the same call to add() is parsed with HTTP::Headers, which takes time quadratic in the number of fields of one name.  For example, it takes several seconds to parse 16 KiB of "a:" lines.

A remote attackercan exhause the CPU with a single request.

HTTP::Body version 1.25 limits the size and number of lines in the trailer.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-121006 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-121006 is a high-severity vulnerability, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121006 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-121006/ (Markdown: https://insights.sbomify.com/CVE-2026-121006/index.md)
```

## Sources

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

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