Quick answers
- Is CVE-2026-54258 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-54258 being exploited in the wild.
- How severe is CVE-2026-54258?
- Medium severity, with a CVSS score of 6.5, published 11 September 2026.
- Which products and versions are affected?
- Zoneminder before 1.36.39, 1.37.0 before 1.38.4, 1.39.0 before 1.39.11.
- Is there a fix for CVE-2026-54258?
- A patch was published on 2026-06-03: Versions 1.36.39, 1.38.4, and 1.39.11 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-54258 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-54258?
- Check whether you run Zoneminder at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is a Broken Object Level Authorization (BOLA) vulnerability in ZoneMinder's direct media endpoints. The vulnerable endpoints (GET /zm/index.php?view=image, GET /zm/index.php?view=view_video, GET /zm/index.php?view=view_hls) check only coarse permission checks like canView('Events') or canView('Snapshots') but fail to enforce per-monitor and per-event access control lists (ACLs) via the $Event->canView() method. An authenticated low-privileged user with broad Events=View or Snapshots=View permissions can bypass monitor-level restrictions by directly supplying an arbitrary event ID (eid parameter) to these endpoints, directly accessing media from restricted monitors. The normal web UI correctly hides restricted monitors and events, but these direct media handlers circumvent that authorization layer. Attack requires valid authentication but no further user interaction. Patches are available in versions 1.36.39, 1.38.4, and 1.39.11.
Affected products
- ZoneMinder ZoneMinder before 1.36.39, 1.37.0 before 1.38.4, 1.39.0 before 1.39.11
Timeline
- 2026-06-03: disclosed: GitHub Security Advisory published
- 2026-06-03: patched: Versions 1.36.39, 1.38.4, and 1.39.11 released