# CVE-2026-114458: Mod_qos: undersized connection-monitor scratch array permits heap buffer overflow


- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-114458, GHSA-vh3m-p78w-c5fp, UBUNTU-CVE-2026-114458

## What is CVE-2026-114458?

CVE-2026-114458 is a medium-severity vulnerability in pbuchbinder mod_qos, published on 22 Oct 2026. 

### Official description

A flaw was found in mod_qos. An unauthenticated remote attacker can cause a Denial of Service (DoS) by maintaining numerous concurrent low-rate connections to a target server. When connection rate monitoring is active, the module fails to verify array boundaries when recording client IP addresses, allowing more connection records to be added than the allocated buffer can hold. This issue leads to heap memory corruption, which can crash the web server process.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-114458 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-114458 is a medium-severity vulnerability in pbuchbinder mod_qos, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-114458 in the wild and no public exploit code.

Affected product: pbuchbinder mod_qos. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-114458/ (Markdown: https://insights.sbomify.com/CVE-2026-114458/index.md)
```

## Sources

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

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