# CVE-2026-33470: Missing authorization in frigate

> A low-privilege user can access snapshots from unauthorized cameras by exploiting missing authorization checks in the API.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 26 Mar 2026
- **Updated:** 26 Mar 2026
- **Also known as:** GHSA-m2mg-pj9p-2r7g

## What is CVE-2026-33470?

CVE-2026-33470 is a medium-severity missing authorization vulnerability in blakeblackshear frigate, published on 26 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Frigate is a network video recorder (NVR) with realtime local object detection for IP cameras. In version 0.17.0, a low-privilege authenticated user restricted to one camera can access snapshots from other cameras. This is possible through a chain of two authorization problems: `/api/timeline` returns timeline entries for cameras outside the caller's allowed camera set, then `/api/events/{event_id}/snapshot-clean.webp` declares `Depends(require_camera_access)` but never actually validates `event.camera` after looking up the event. Together, this allows a restricted user to enumerate event IDs from unauthorized cameras and then fetch clean snapshots for those events. Version 0.17.1 fixes the issue.

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Frigate Frigate.

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

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

## Is CVE-2026-33470 being exploited?

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

## Other vulnerabilities in blakeblackshear frigate

- [CVE-2026-25643](https://insights.sbomify.com/CVE-2026-25643/): Frigate Affected by Authenticated Remote Command Execution (RCE) and Container Escape (critical 9.1)
- [CVE-2026-33124](https://insights.sbomify.com/CVE-2026-33124/): Frigate has insecure password change functionality (high 8.6)
- [CVE-2023-45670](https://insights.sbomify.com/CVE-2023-45670/): Frigate cross-site request forgery in `config_save` and `config_set` request handlers (high 7.5)
- [CVE-2023-45672](https://insights.sbomify.com/CVE-2023-45672/): Frigate unsafe deserialization in `load_config_with_no_duplicates` of `frigate/util/builtin.py` (high 7.5)
- [CVE-2026-33125](https://insights.sbomify.com/CVE-2026-33125/): Frigate Broken Access Control: Users assigned the viewer role can delete admin and other low-privileged accounts (high 7.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-33470 is a medium-severity missing authorization vulnerability in blakeblackshear frigate, published on 26 Mar 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-33470 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-33470/ (Markdown: https://insights.sbomify.com/CVE-2026-33470/index.md)
```

## Sources

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

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