Frigate is an open source network video recorder. Prior to 0.18.0, the prefix-matched location /api/go2rtc/api in docker/main/rootfs/usr/local/nginx/conf/nginx.conf requires authentication but does not require an administrator role for GET requests, exposing the proxied go2rtc API to viewer users. An authenticated viewer can request the streams, config, log, and stack subpaths to obtain internal addresses, configuration paths, application logs, goroutine stack data, and RTSP stream URLs that may contain camera credentials. Non-GET methods remain blocked by limit_except GET. This issue is fixed in version 0.18.0.
CVE-2026-75608
This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 7.7
- EG Score
- 7.7(low)
- EG Risk
- 39(Track)EG Risk 39/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity77% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 43%
- KEV
- Not listed
Published
September 22, 2026
Last Modified
September 22, 2026
Advisory Details (4)
Auto-updated Sep 22, 20260.18.0 Release
Patch available: blakeblackshear/frigate v0.18.0
https://github.com/blakeblackshear/frigate/releases/tag/v0.18.0commit 520d9eeb7f0f (blakeblackshear/frigate)
Fix landed in blakeblackshear/frigate commit 520d9eeb7f0f — awaiting tagged release
https://github.com/blakeblackshear/frigate/commit/520d9eeb7f0fe46021f29fb8169741dd1d429271Remove direct go2rtc API proxy in favor of frigate API endpoints
Fix merged in blakeblackshear/frigate PR #22735 on 2026-04-02 — awaiting tagged release
https://github.com/blakeblackshear/frigate/pull/22735Viewer-Role User Can Access go2rtc Internal API to obtain sensitive information · Advisory · blakeblackshear/frigate · GitHub
https://github.com/blakeblackshear/frigate/security/advisories/GHSA-mgh5-cr9h-g6hrWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-23 17:54 UTCEPSS rescore
- 2026-09-22 16:19 UTCEG score recompute
- 2026-09-22 15:45 UTCEG score recompute
- 2026-09-22 15:44 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-863
Frequently asked(5)
What is CVE-2026-75608?
When was CVE-2026-75608 disclosed?
Is CVE-2026-75608 actively exploited?
What is the CVSS score of CVE-2026-75608?
How do I remediate CVE-2026-75608?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75608
Is Your Infrastructure Affected by CVE-2026-75608?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.