# CVE-2026-116531: HTTP::Body versions before 1.23_01 for Perl lose track of chunk boundaries in chunked request bodies when a read ends inside a chunk.


- **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-116531, GHSA-288c-cm7p-6mc5

## What is CVE-2026-116531?

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

### Official description

HTTP::Body versions before 1.23_01 for Perl lose track of chunk boundaries in chunked request bodies when a read ends inside a chunk.

In chunked mode, used when no content length is given, add() treats a chunk as complete once the buffer is as long as the chunk's declared size, but the buffer still holds the chunk-size line. When a read ends in the last bytes of a chunk, add() takes the chunk short and parses the leftover data as the next chunk-size line.

A remote attacker can make a chunked body never complete, hanging a server that reads until the body is done, and may make it complete early, leaving the remaining bytes to be read as the next request.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

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


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

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

## Is CVE-2026-116531 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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