# CVE-2026-113877: HTTP::Headers::ActionPack versions before 0.10 for Perl allow CPU exhaustion via Accept-Language ranges matched as regular expressions.


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-113877, GHSA-q4hv-hfj9-x4r5

## What is CVE-2026-113877?

CVE-2026-113877 is a vulnerability, published on 23 Oct 2026. 

### Official description

HTTP::Headers::ActionPack versions before 0.10 for Perl allow CPU exhaustion via Accept-Language ranges matched as regular expressions.

_language_match interpolates each Accept-Language range into the pattern `/^$range\-/i` without escaping it, so regular expression syntax in the header reaches the regex engine. A 12-byte range such as `(a?|b?){26}z` backtracks for seconds, and each increment of the quantifier doubles the time. An invalid range such as `(` fails to compile.

A remote attacker can exhaust CPU, or make choose_language die, in any application that passes an untrusted Accept-Language header to it.

Weakness: CWE-624 (Executable Regular Expression Error)

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


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

Upgrade to a fixed version.

## Is CVE-2026-113877 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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