VulnerabilityPublished 28 Sep 2026Updated 17 Oct 2026

CVE-2026-102297: ZoneMinder before 1.38.4 fails to apply per-monitor access restrictions in the FramesController index endpoint

Affects zoneminderSource GCVE Database

Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 1.38.4 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.38.4

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-xfq3-f9p9-wv2c

What to do

Upgrade zoneminder/zoneminder to 1.38.4.

Affected software

Product	Affected	Fixed in
GitHubzoneminder/zoneminder`pkg:github/zoneminder/zoneminder`Other threats	Affected <1.38.4	Fixed in 1.38.4
Ubuntu Pro 16.04 LTSzoneminder`pkg:deb/ubuntu/zoneminder?arch=source&distro=esm-apps/xenial`Other threats	Affected 1.28.1-8 – 1.29.0+dfsg-1ubuntu2+esm1 5 affected builds	Fixed in–
Ubuntu Pro 20.04 LTSzoneminder`pkg:deb/ubuntu/zoneminder?arch=source&distro=esm-apps/focal`Other threats	Affected 1.32.3-2build1 – 1.32.3-2ubuntu2+esm1 4 affected builds	Fixed in–
Ubuntu Pro 22.04 LTSzoneminder`pkg:deb/ubuntu/zoneminder?arch=source&distro=esm-apps/jammy`Other threats	Affected 1.36.7+dfsg1-1 – 1.36.12+dfsg1-1ubuntu0.1~esm1 5 affected builds	Fixed in–
Ubuntu 24.04 LTSzoneminder`pkg:deb/ubuntu/zoneminder?arch=source&distro=noble`Other threats	Affected 1.36.33+dfsg1-1build1 – 1.36.33+dfsg1-1build4 4 affected builds	Fixed in–
Ubuntu 26.10zoneminder`pkg:deb/ubuntu/zoneminder?arch=source&distro=stonking`Other threats	Affected =1.36.37+dfsg1-1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in ZoneMinder version 1.38.4 and later. Users should upgrade to version 1.38.4 or newer to remediate this issue. No vendor advisory content was provided, but the version information clearly indicates that versions before 1.38.4 are affected and the issue is fixed in 1.38.4.

Description

ZoneMinder versions before 1.38.4 have a vulnerability where per-monitor access restrictions are not enforced in the FramesController index endpoint. Authenticated users with Events view permission can access frame records from monitors they should not have access to, leading to unauthorized disclosure of event and frame metadata across monitor boundaries. The vulnerability has a medium severity with a CVSS score of 4.3.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Oct 2026, 01:56 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats