CVE-2026-25643
Critical RCE via unsanitized config.yaml in Frigate-go2rtc.
Is CVE-2026-25643 being exploited?
Not confirmed. CVE-2026-25643 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 2.9% probability of exploitation in the next 30 days.
How severe is CVE-2026-25643?
CVE-2026-25643 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-25643?
Yes. A fix has been recorded for CVE-2026-25643. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-25643 affect?
CVE-2026-25643 affects Frigate NVR (pre-0.16.4), go2rtc integration. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-25643?
Upgrade to 0.16.4+; restrict internet exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE via unsanitized config.yaml in Frigate-go2rtc; internet-exposed admins gain full control.
Immediate action required
- affected< 0.16.4
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.