Viewer credential disclosure via overbroad go2rtc proxy
Published Sep 22, 2026 · Updated Sep 22, 2026
Incorrect authorization in Frigate before 0.18.0 allows remote authenticated users with viewer access to read sensitive go2rtc data. The nginx prefix location /api/go2rtc/api authenticates GET requests but never checks for the administrator role before proxying every go2rtc API subpath. A valid viewer account is required; exposed data includes internal addresses, logs, stack traces, configuration paths, and RTSP URLs containing camera credentials.
Summary
What happened
Incorrect authorization in Frigate before 0.18.0 allows remote authenticated users with viewer access to read sensitive go2rtc data. The nginx prefix location /api/go2rtc/api authenticates GET requests but never checks for the administrator role before proxying every go2rtc API subpath. A valid viewer account is required; exposed data includes internal addresses, logs, stack traces, configuration paths, and RTSP URLs containing camera credentials.
The record
- CVE
- CVE-2026-75608
- Published
- Sep 22, 2026
- Updated
- Sep 22, 2026
- Vendor
- Frigate, Inc.
- Product
- Frigate
- Classifications
- CWE-863, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 22, 2026CVE publishedPublication date reported by the CVE source.
- Sep 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.18.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
- Viewer-role go2rtc API reproduction requestsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started