PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-75608 blakeblackshear CVE debrief

CVE-2026-75608 Frigate API Exposure. Frigate is an open source network video recorder with an authentication bypass vulnerability in versions prior to 0.18.0. The /api/go2rtc/api path in nginx.conf requires authentication but does not enforce administrator roles for GET requests, allowing authenticated viewer users to access internal addresses, configuration paths, application logs, goroutine stack data, and RTSP stream URLs that may contain camera credentials. Defenders responsible for Frigate deployments, particularly those with viewer user roles, should assess exposure and prioritize updating to version 0.18.0 or later to mitigate potential information disclosure.

Vendor
blakeblackshear
Product
frigate
CVSS
HIGH 7.7
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-22
Original CVE updated
2026-09-28
Advisory published
2026-09-22
Advisory updated
2026-09-28

Who should care

Defenders responsible for Frigate deployments, particularly those with viewer user roles, should assess exposure and prioritize updating to version 0.18.0 or later to mitigate potential information disclosure.

Why it matters

CVE-2026-75608 allows authenticated viewer users in Frigate versions prior to 0.18.0 to access sensitive information via the go2rtc API, potentially disclosing internal addresses, configuration paths, application logs, goroutine stack data, and RTSP stream URLs that may contain camera credentials. Defenders should prioritize updating to version 0.18.0 or later and restrict access to go2rtc API endpoints to administrator roles.

  • Authenticated viewers may have accessed internal addresses and configuration paths
  • Exposure of application logs and goroutine stack data may have occurred
  • RTSP stream URLs potentially containing camera credentials may have been disclosed
  • Verification of authentication and authorization for API requests is necessary

Technical summary

Frigate versions prior to 0.18.0 contain an authentication bypass vulnerability in the go2rtc API. The /api/go2rtc/api path in nginx.conf requires authentication but does not enforce administrator roles for GET requests, allowing authenticated viewer users to access internal addresses, configuration paths, application logs, goroutine stack data, and RTSP stream URLs that may contain camera credentials.

Defensive priority

Authenticated users with viewer roles may have been able to access sensitive information via the go2rtc API prior to Frigate version 0.18.0.

Recommended defensive actions

  • Review and update Frigate deployments to version 0.18.0 or later
  • Restrict access to go2rtc API endpoints to administrator roles
  • Monitor for and limit exposure of internal addresses and camera credentials
  • Verify authentication and authorization for API requests
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review

Evidence notes

The CVE record and NVD entry detail an authentication bypass in Frigate versions prior to 0.18.0, allowing viewers to access go2rtc API endpoints. Official CVE and NVD records provide vulnerability details.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-75608 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-75608

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-75608 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-75608

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.