Description

Frigate is an open source network video recorder. Prior to 0.17.2, the WebSocket handler in frigate/comms/ws.py forwards attacker-selected message topics to the dispatcher without checking the authenticated user's role because the nginx authentication subrequest does not provide role-aware authorization to the handler. Any authenticated viewer can send admin-only topics such as restart, notifications/set, and camera detection, recording, snapshot, audio, motion, and enablement settings, causing service restarts or disabling security monitoring functions. Authentication must be enabled and valid viewer credentials are required. This issue is fixed in version 0.17.2.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "8.1",
  "pubDate": "2026-09-22T16:17:54.430Z",
  "pubdate": "2026-09-22T16:17:54.430Z",
  "executiveSummary": "Frigate versions prior to 0.17.2 contain a critical broken access control vulnerability within the WebSocket handler. The flaw arises from an inadequate authorization check during the message dispatch process, where the system fails to validate user roles against the requested message topic.\nThis vulnerability allows any authenticated viewer—regardless of their assigned privilege level—to execute sensitive administrative functions. By crafting malicious WebSocket messages, an attacker can trigger service restarts or manipulate core security monitoring configurations, including the disabling of cameras, recording, and detection systems.\nExploitation requires valid user credentials and that authentication is enabled on the instance. The impact is significant, as it effectively grants standard users full administrative control over the NVR's operational state, potentially blinding security monitoring services. Organizations relying on Frigate for surveillance should prioritize an immediate upgrade to version 0.17.2 to resolve this authorization bypass.",
  "technicalDetails": "The vulnerability is localized within the file 'frigate/comms/ws.py', specifically within the WebSocket message handling logic. The root cause is a failure to implement role-based access control (RBAC) at the handler level when processing incoming WebSocket messages.\nIn the affected versions, the Frigate architecture utilizes an nginx authentication subrequest mechanism. While this mechanism effectively handles initial authentication, it fails to propagate granular user-role information to the internal dispatcher. Consequently, the dispatcher assumes that any message arriving from a session that has passed the initial authentication check is authorized to execute its associated command.\nThe attack flow begins with an attacker establishing an authenticated WebSocket connection to the Frigate instance. Once the session is established, the attacker sends a crafted JSON message to the WebSocket handler. Because the application logic does not perform a secondary validation of the authenticated user's role before processing the 'topic' field, the dispatcher blindly accepts administrative commands. By specifying topics such as 'restart', 'notifications/set', or specific camera control parameters like 'detection', 'recording', 'snapshot', 'audio', 'motion', and general 'enablement' settings, the attacker can manipulate the NVR's state.\nThis effectively bypasses the distinction between a 'viewer' role and an 'admin' role. The payload behavior involves the dispatcher passing the attacker-supplied topic and associated data directly to the underlying service management components. Post-exploitation impact includes the total loss of availability (via service restart) and the compromise of confidentiality and integrity regarding security monitoring operations. Because the handler does not differentiate between a non-privileged user's request and a privileged request, the dispatcher performs unauthorized state changes with the permissions of the service process itself. The vulnerability is present in all versions prior to 0.17.2, where the lack of role-aware authorization enables any authenticated entity to perform high-privilege operations, violating the principle of least privilege."
}