Quick answers
- Is CVE-2026-117500 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-117500 being exploited in the wild.
- How severe is CVE-2026-117500?
- 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-117500?
- Yes: fixed in HTTP::Body 1.24_01. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-117500 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-117500?
- 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
Technical details
The vulnerability exists in the default $basename_regexp pattern used to extract file extensions from multipart upload filenames. A malicious filename constructed with many dots and a trailing backslash causes the regex engine to exhibit catastrophic backtracking, taking time quadratic in the filename length (7 seconds per part at the 32 KiB header limit). The fix replaces the regex with a linear-time string search for the default pattern while preserving the regex for custom patterns.
Affected products
- Perl HTTP::Body before 1.24_01
Timeline
- 2026-10-28: disclosed
- 2026-10-28: advisory