CVE-2026-72556 ZoneMinder CVE debrief

Who should care

Administrators and users of ZoneMinder 1.39.17, as well as security teams responsible for monitoring and patching vulnerabilities, should prioritize patching and restrict user permissions to minimize the impact of the vulnerability. Additionally, security teams should review compensating controls for exposed systems while remediation is scheduled and verified, and check relevant monitoring, detection, and logs for exposed assets that need extra review. Asset inventory and vulnerability management teams should also be aware of the potential impact on their systems and prioritize patching accordingly. Security teams should track exceptions, retest remediated assets, and close the item only after evidence is documented. This vulnerability affects operators, platforms, and security teams that rely on ZoneMinder 1.39.17 for monitoring and security purposes. The vulnerability's impact on these teams is significant, as it allows any authenticated user to execute OS commands, potentially leading to a compromise of the system. Therefore, it is essential for these teams to take immediate action to patch the vulnerability and restrict user permissions to prevent exploitation. The vulnerability also affects security teams that are responsible for monitoring and patching vulnerabilities, as they need to prioritize patching and verify the effectiveness of compensating controls. Overall, the vulnerability has a significant impact on various teams and requires immediate attention to prevent exploitation. The vulnerability's severity and potential impact on these teams emphasize the need for prompt action to mitigate the vulnerability. The vulnerability affects a wide range of stakeholders, including administrators, users, and security teams, who must work together to address the vulnerability and prevent potential attacks. The vulnerability's impact on these stakeholders is substantial, and it is crucial that they take immediate action to patch the vulnerability and prevent exploitation. The vulnerability's severity and potential impact on these stakeholders highlight the need for prompt action to mitigate the vulnerability and prevent potential attacks. The vulnerability has a

Technical summary

The CVE-2026-72556 vulnerability is caused by a broken permission check in the Filter class of ZoneMinder 1.39.17. The canEdit() and canDelete() methods invoke nonexistent methods on the ZM/User class, causing PHP __call() to return a truthy value that bypasses the permission check for all users. This allows any authenticated user to execute OS commands. The vulnerability has a CVSS score of 8.8 and is classified as HIGH. To exploit this vulnerability, an attacker would need to be an authenticated user and have the ability to trigger filter-based OS command execution.

Defensive priority

Authenticated users can execute OS commands; prioritize patching and restrict user permissions.

Recommended defensive actions

• Apply patches or updates provided by the vendor to fix the broken permission check in the Filter class.
• Restrict user permissions to minimize the impact of the vulnerability.
• Monitor system logs for suspicious activity related to OS command execution.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Review compensating controls for exposed systems while remediation is scheduled and verified.
• Check relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.

Evidence notes

The CVE-2026-72556 record indicates a remote code execution vulnerability in ZoneMinder 1.39.17. The canEdit() and canDelete() methods in the Filter class have a broken permission check, allowing any authenticated user to execute OS commands. The vulnerability has a CVSS score of 8.8 and is classified as HIGH.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.