Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS scores by FIRST (EPSS SIG), generated by Empirical Security. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-25643 is a critical-severity OS Command Injection (CWE-78) vulnerability in Frigate. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 13% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-2 (Account Management) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-25643 is a critical remote command execution (RCE) vulnerability affecting Frigate, an open-source network video recorder (NVR) with realtime local object detection for IP cameras, in versions prior to 0.16.4. The issue resides in the Frigate integration with go2rtc, where the application fails to sanitize user input within the video stream configuration file (config.yaml). This allows attackers to inject arbitrary system commands using the exec: directive, which the go2rtc service then executes without restrictions. The vulnerability is associated with CWEs-78 (OS Command Injection), CWE-250 (Execution with Unnecessary Privileges), CWE-269 (Improper Privilege Management), and CWE-668 (Excessive Exposure of Sensitive Information to an Unauthorized Process), and carries a CVSS v3.1 base score of 9.1 (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
Exploitation requires high privileges, specifically an administrator account, though it becomes accessible to unauthenticated remote attackers if the Frigate installation is exposed to the open internet without authentication controls. Successful exploitation grants full administrative control over the system, enabling complete confidentiality, integrity, and availability impacts through arbitrary command execution on the host.
The vulnerability has been addressed in Frigate version 0.16.4, as detailed in the official release notes and GitHub security advisory GHSA-4c97-5jmr-8f6x. Security practitioners should immediately upgrade to 0.16.4 or later, ensure Frigate instances are not exposed to the public internet without authentication, and review config.yaml files for any malicious exec: directives.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-5586
Vulnerability Data
Frigate is a network video recorder (NVR) with realtime local object detection for IP cameras. Prior to 0.16.4, a critical Remote Command Execution (RCE) vulnerability has been identified in the Frigate integration with go2rtc. The application does not sanitize user…
more
input in the video stream configuration (config.yaml), allowing direct injection of system commands via the exec: directive. The go2rtc service executes these commands without restrictions. This vulnerability is only exploitable by an administrator or users who have exposed their Frigate install to the open internet with no authentication which allows anyone full administrative control. This vulnerability is fixed in 0.16.4.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 4 hardening rules · 4 OS baselines
V10.2.3V13.2.2V1.2.5V1.2.8
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops resources from being reachable by actors outside the intended control sphere.
Account management directly governs assignment and tracking of privileges so proper implementation stops the weakness from being introduced.
Requiring explicit access-control decisions ensures privileges are evaluated rather than assumed or omitted.
Information flow enforcement structurally prevents unintended cross-sphere data or resource exposure.
Separation of duties constrains how privileges may be assigned, reducing the chance of overly broad actor control.
Least privilege directly requires that only the minimum necessary authorizations are granted, structurally eliminating execution with unnecessary privileges.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
PR.AA-05 directly enforces least privilege so largely eliminates CWE-250 at design time, yet the weakness can still arise from runtime escalation paths, third-party code, or misapplied role definitions outside this single control.
PR.PS-06's SDLC practices directly require secure coding and input handling that blocks command-injection defects, yet the single broad outcome leaves many specific neutralization vectors and verification gaps unaddressed.
Routine patching/maintenance can remediate known command-injection CVEs in dependencies (partial forward) but does nothing to stop developers from introducing improper neutralization in custom code (none reverse).
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
A.5.15's policy, requirements, and rules for determining/minimizing access rights (incl. privileged access restrictions, need-to-know, least-privilege-like mapping, and role-based consistency) directly stop most unnecessary-privilege execution by design; bounded remainder is runtime elevation or misconfigured enforcement that still requires other controls (e.g. 8.2, 8.3) to act.
Requiring explicit justification and time-limited grants discourages the routine allocation of unnecessary privileges that would otherwise allow execution with more rights than required.
A.8.18's guidelines (esp. a,b,c,d,e,f,h,i) directly limit who, when, and how privileged utilities run, stopping most unnecessary-privilege execution from being exploitable; the bounded remainder is utilities whose use cannot be fully segregated or time-boxed without breaking legitimate admin work.
A.8.2 directly controls allocation, review, temporary/just-in-time grant, least-privilege-per-role, and separation of privileged vs normal identities, which stops most unnecessary-privilege execution (the core of CWE-250); the bounded remainder is cases where the granted rights still exceed what the approved role actually needs in that moment.
Security testing and code review target insecure use of operating-system command interfaces, catching command-injection flaws introduced during development.
A.8.3 directly restricts access per policies (config mechanisms, per-user/group rights, isolation, dynamic techniques, auth/credential enforcement), which stops exploitation of most improper privilege management cases even if the assignment/tracking flaw remains; named remainder exists for non-access-control privilege errors (e.g. pure assignment bugs outside enforcement).
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Windows 10 (1 rule)
- V-220712 Only accounts responsible for the administration of a system must have Administrator rights on the system. blocks CWE-250
Windows Server 2016 (1 rule)
- V-225007 Only administrators responsible for the member server or standalone or nondomain-joined system must have Administrator rights on the system. blocks CWE-250
Windows Server 2019 (1 rule)
- V-205746 Windows Server 2019 must only allow Administrators responsible for the member server or standalone or nondomain-joined system to have Administrator rights on the system. blocks CWE-250