# CVE-2026-102297: ZoneMinder before 1.38.4 Incorrect Authorization in frames API index

> Authenticated users can bypass monitor access restrictions to view frame metadata from unauthorized monitors in ZoneMinder.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **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-102297, GHSA-mg2g-jmfc-3w8g, GHSA-xfq3-f9p9-wv2c, UBUNTU-CVE-2026-102297

## What is CVE-2026-102297?

CVE-2026-102297 is a medium-severity missing authorization vulnerability in zoneminder, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZoneMinder before 1.38.4 fails to apply per-monitor access restrictions in the FramesController index endpoint. Authenticated users with Events view permission can call the frames API to list frame records from monitors they are denied access to, disclosing event and frame metadata across monitor boundaries.

Weakness: CWE-863 (Incorrect Authorization)

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


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

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

## Is CVE-2026-102297 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102297 is a medium-severity missing authorization vulnerability in zoneminder, published on 28 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-102297 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-102297/ (Markdown: https://insights.sbomify.com/CVE-2026-102297/index.md)
```

## Sources

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

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