# CVE-2025-62382: Frigate Vulnerable to Arbitrary File Read via Export Thumbnail "image_path" parameter

> An authenticated user can read arbitrary files from the host by manipulating the export thumbnail path, leading to information disclosure.

- **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:** 15 Oct 2025
- **Updated:** 17 Oct 2025
- **Also known as:** GHSA-8gv4-5jr9-v96j

## What is CVE-2025-62382?

CVE-2025-62382 is a high-severity path traversal vulnerability in blakeblackshear frigate, published on 15 Oct 2025. 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. Prior to 0.16.2, Frigate's export workflow allows an authenticated operator to nominate any filesystem location as the thumbnail source for a video export. Because that path is copied verbatim into the publicly served clips directory, the feature can be abused to read arbitrary files that reside on the host running Frigate. In practice, a low-privilege user with API access can pivot from viewing camera footage to exfiltrating sensitive configuration files, secrets, or user data from the appliance itself. This behavior violates the principle of least privilege for the export subsystem and turns a convenience feature into a direct information disclosure vector, with exploitation hinging on a short race window while the background exporter copies the chosen file into place before cleanup runs. This vulnerability is fixed in 0.16.2.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2025-62382?


## How do I fix CVE-2025-62382?

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

## Is CVE-2025-62382 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62382 and fix it if it is affected.

What it is: CVE-2025-62382 is a high-severity path traversal vulnerability in blakeblackshear frigate, published on 15 Oct 2025. 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-2025-62382 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-2025-62382/ (Markdown: https://insights.sbomify.com/CVE-2025-62382/index.md)
```

## Sources

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

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