CVE-2026-54652
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFrigate is an open source network video recorder. In version 0.17.1, the GET /api/logs/{service} endpoint allows any authenticated user including the viewer role to download Frigate and nginx logs, exposing auto-generated admin passwords and camera credentials logged in request query strings and enabling viewer-to-admin privilege escalation. A fixed release has not been identified.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe GET /api/logs/{service} endpoint in Frigate 0.17.1 lacks proper role-based authorization, allowing any authenticated user including those with the viewer role to download system logs. This exposes sensitive credentials including auto-generated admin passwords and camera authentication details logged in query strings, enabling privilege escalation from viewer to admin.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Frigate versionCheck the installed Frigate version (typically via docker image tag, UI footer, or config file)Affected if Running version 0.17.1 or any version in the 0.17.x line prior to any available patch
-
Verify API endpoint accessibilityConfirm the Frigate API is network-accessible (check firewall rules, reverse proxy config, or service binding)Affected if The /api/logs/{service} endpoint is reachable from untrusted networks or by non-admin users
-
Review user role configurationInspect Frigate's authentication configuration to determine if viewer roles are configured and enabledAffected if Viewer role accounts exist and are permitted to authenticate to the API
-
Test endpoint authorizationAttempt to access GET /api/logs/{service} using a viewer-level account (or inspect API access control configuration)Affected if Viewer role can retrieve log data from the endpoint without admin privileges
-
Audit logs for credential exposureExamine stored or live Frigate logs for sensitive strings such as passwords, API keys, or authentication tokens in query parametersAffected if Logs contain plaintext credentials, auto-generated admin passwords, or camera authentication details
You are affected if running Frigate 0.17.x with the API accessible to viewer-role users who can retrieve system logs containing sensitive credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataSince no patched version is available, restrict network access to the Frigate API, implement additional authentication gateway or Web Application Firewall in front of the service, and audit logs for unauthorized access to the /api/logs endpoint until an official fix is released.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54652 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-54652 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data