Skip to content
IoT

CVE-2026-54652

8.1
High
EPSS 0.41%Patch availableJul 9, 2026

Authenticated viewer can download logs exposing admin and camera credentials.

common questions

Is CVE-2026-54652 being exploited?

Not confirmed. CVE-2026-54652 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 0.41% probability of exploitation in the next 30 days.

How severe is CVE-2026-54652?

CVE-2026-54652 is rated High with a CVSS score of 8.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-54652?

Yes. A fix has been recorded for CVE-2026-54652. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-54652 affect?

CVE-2026-54652 affects Frigate NVR 0.17.1, Frigate deployments exposing /api/logs/{service}, nginx logs with query-string credentials. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-54652?

Restrict viewer access, disable/limit /api/logs, rotate exposed credentials, monitor for vendor patch.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Frigate NVR 0.17.1Frigate deployments exposing /api/logs/{service}nginx logs with query-string credentials
impact

Authenticated viewer can retrieve logs containing admin passwords and camera credentials, enabling viewer-to-admin privilege escalation and potential device/account takeover.

action required

Immediate action required

affected versions
blakeblackshear frigate
  • affected<= 0.17.1

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free