# CVE-2026-117500: HTTP::Body versions before 1.24_01 for Perl allow CPU exhaustion via regex backtracking on the filename of a multipart upload.


- **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-117500, GHSA-w2gq-c2cx-w9q6

## What is CVE-2026-117500?

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

### Official description

HTTP::Body versions before 1.24_01 for Perl allow CPU exhaustion via regex backtracking on the filename of a multipart upload.

For every file part, the multipart parser finds the suffix of the uploaded filename by matching the default $basename_regexp, qr/[^.]+(\.[^\\\/]+)$/, against the whole basename. A basename made of many dots and ending in a backslash makes the regex backtrack in time quadratic in its length.

A remote attacker can exhaust CPU with one request, as a basename of about 32 KB takes several seconds to match and every file part is matched separately.

Weakness: CWE-1333 (Inefficient Regular Expression Complexity)

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


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

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

## Is CVE-2026-117500 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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