# CVE-2026-102296: ZoneMinder before 1.38.4 Buffer Overflow via HTTP Camera Response

> Attackers can cause memory corruption or crashes in ZoneMinder by sending oversized HTTP responses from malicious cameras or via interception.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 6 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-102296, GHSA-93j4-rcp9-9jx6, GHSA-9748-j7v2-wg49, UBUNTU-CVE-2026-102296

## What is CVE-2026-102296?

CVE-2026-102296 is a high-severity memory corruption vulnerability in zoneminder, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ZoneMinder before 1.38.4 contains static buffer overflow vulnerabilities in RemoteCameraHttp::GetResponse() that allow malicious HTTP cameras or intercepting attackers to overflow fixed-size buffers by sending oversized response headers. Attackers can send crafted HTTP responses with oversized status messages, Connection headers, Content-Type values, or multipart boundaries to corrupt parser state and crash the capture process or corrupt memory.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2026-102296 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102296 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102296 is a high-severity memory corruption vulnerability in zoneminder, published on 28 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102296 exists.

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

## Sources

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

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