Quick answers
- Is CVE-2026-117501 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117501 being exploited in the wild.
- How severe is CVE-2026-117501?
- Informational severity, published 28 October 2026.
- Which products and versions are affected?
- Perl HTTP::Body before 1.24_01.
- Is there a fix for CVE-2026-117501?
- Yes: fixed in HTTP::Body 1.24_01. Until then: Limit the maximum chunk-size line length using the $HTTP::Body::max_chunk_line_size configuration variable (default 1024 bytes); set it to 0 to disable chunked parsing entirely if chunked transfer encoding is not required by your application. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117501 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-117501?
- Check whether you run Perl 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.24_01
Limit the maximum chunk-size line length using the $HTTP::Body::max_chunk_line_size configuration variable (default 1024 bytes); set it to 0 to disable chunked parsing entirely if chunked transfer encoding is not required by your application.
Technical details
The vulnerability exists in the chunked request body parser when no Content-Length header is provided. Malformed input—such as a chunk-size line without CRLF, a size value that overflows an integer, or invalid framing—causes the parser to stall while buffering grows unbounded on each subsequent add() call. The attacker must be able to send HTTP requests with chunked transfer encoding to a vulnerable application.
Affected products
- Perl HTTP::Body before 1.24_01
Timeline
- 2026-10-28: disclosed
- 2026-10-26: patched: Patch committed to repository