# CVE-2026-116131: libhttp-body-perl: HTTP::Body versions before 1.23_01 for Perl allow memory and temporary file exhaustion via an unlimited number of for...

CVE-2026-116131 is fixed in libhttp-body-perl on 1 platform by DEBIAN-CVE-2026-116131 (version 1.24.01-1), released November 3, 2026. It is not reported as exploited. Patch Radar priority: Routine.

- Web page: https://patchblox.com/security/cve/CVE-2026-116131
- Priority: Routine
- CVSS: 6.5 (medium)
- EPSS: 0.0042
- CISA KEV: not listed
- Exploited (vendor report): no
- Publicly disclosed: no
- Published: Oct 28, 2026

## Description

HTTP::Body versions before 1.23_01 for Perl allow memory and temporary file exhaustion via an unlimited number of form fields and multipart parts.  The urlencoded parser splits the whole body on its separators at once, creating one scalar per separator before any field is stored. This costs about 90 bytes of memory per separator byte. The multipart parser creates a temporary file for every part that carries a filename. Neither parser limits how many fields or parts a body may hold.  A remote attacker can exhaust worker memory with a body made of separators, or create thousands of temporary files with one request of small file parts.

## Where it's fixed

| Platform | Product | Fixed in | Fix | Released |
|---|---|---|---|---|
| Linux | libhttp-body-perl Debian 14 | 1.24.01-1 | [DEBIAN-CVE-2026-116131](https://patchblox.com/security/data/fix/linux/debian-cve-2026-116131.md) | Nov 3, 2026 |

---

Data as of 2026-11-09T07:25:28Z UTC. Source: Patchblox Patch Radar (https://patchblox.com/security/patch-radar). Patchblox finds out-of-date software on Windows, macOS and Linux and updates it through release rings: https://patchblox.com/demo

Free to use with attribution: show "Data: Patchblox Patch Radar" with a link to https://patchblox.com/security/patch-radar. Terms, including what needs a written agreement: https://patchblox.com/security/patch-radar/use-the-data

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.