# CVE-2026-75608: Frigate: Viewer-Role User Can Access go2rtc Internal API to obtain sensitive information

> Authenticated viewer users can access internal go2rtc API endpoints to retrieve sensitive configuration data and camera credentials.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Sep 2026
- **Updated:** 28 Sep 2026
- **Also known as:** GHSA-mgh5-cr9h-g6hr

## What is CVE-2026-75608?

CVE-2026-75608 is a high-severity missing authorization vulnerability in blakeblackshear frigate, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-75608?


## How do I fix CVE-2026-75608?

No fix has been published for CVE-2026-75608 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-75608 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75608 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75608 and fix it if it is affected.

What it is: CVE-2026-75608 is a high-severity missing authorization vulnerability in blakeblackshear frigate, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75608 exists.

Affected product: blakeblackshear frigate. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75608/ (Markdown: https://insights.sbomify.com/CVE-2026-75608/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75608
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75608
- OSV: https://osv.dev/vulnerability/CVE-2026-75608

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75608/
Summaries are generated and may contain mistakes; the official description above is the record.