Quick answers
- Is CVE-2026-116134 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-116134 being exploited in the wild.
- How severe is CVE-2026-116134?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- CPAN HTTP::Body before 1.23_01.
- Is there a fix for CVE-2026-116134?
- Yes: fixed in HTTP::Body 1.23_01. Until then: Set $HTTP::Body::MultiPart::max_header_size and $HTTP::Body::MultiPart::max_header_lines to appropriate limits in your application (defaults are 32 KiB and 100 lines respectively); or disable multipart parsing if not required. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-116134 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-116134?
- Check whether you run CPAN HTTP::Body at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: HTTP::Body 1.23_01
Set $HTTP::Body::MultiPart::max_header_size and $HTTP::Body::MultiPart::max_header_lines to appropriate limits in your application (defaults are 32 KiB and 100 lines respectively); or disable multipart parsing if not required.
Technical details
The multipart parser in HTTP::Body does not limit the size or line count of a part's header block (the headers preceding the first blank line after a boundary marker). Each line is stored in a header hash, resulting in approximately 60 bytes of memory overhead per input byte. An unauthenticated remote attacker can trigger memory exhaustion with a single malicious request, causing worker process crashes or system resource depletion.
Affected products
- CPAN HTTP::Body before 1.23_01
Timeline
- 2026-10-28: disclosed
- 2026-10-25: patched: Fix committed to repository