# CVE-2026-116132: HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk


- **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-116132, GHSA-x8v7-c392-2j82

## What is CVE-2026-116132?

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

### Official description

HTTP::Body versions before 1.23_01 for Perl leave the temporary file of an incomplete multipart upload on disk.

The multipart parser creates a temporary file as soon as a file part starts, but adds it to the upload list only when the part completes. Uploads are only ever deleted from that list, by the cleanup option or by the caller, so a body that ends inside a file part leaves its temporary file where nothing can find it.

A remote attacker can fill the temporary directory by repeating such requests, leaving one file behind for each.

Weakness: CWE-459 (Incomplete Cleanup)

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


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

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

## Is CVE-2026-116132 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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