# CVE-2026-130874: Seerr before 3.5.2 Unauthenticated Disk Exhaustion via /imageproxy Cache Keys


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 17 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-849x-56wc-5rrv, GHSA-f5q8-xqg9-97x8

## What is CVE-2026-130874?

CVE-2026-130874 is a high-severity vulnerability in seerr-team Seerr, published on 17 Nov 2026. 

### Official description

Seerr before 3.5.2 contains an uncontrolled resource consumption vulnerability that allows unauthenticated attackers to exhaust disk space through unnormalized /imageproxy cache keys. Attackers can request the same TMDB image using many equivalent dot-segment path spellings, storing unlimited duplicate copies that fill the shared SQLite configuration volume and break logins and requests.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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

1 open source package ship an affected version, including seerr-team/seerr.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `seerr-team/seerr` | GitHub | `pkg:github/seerr-team/seerr` | All versions | 3.5.2 |

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

Upgrade seerr-team/seerr to 3.5.2 or later.

## Is CVE-2026-130874 being exploited?

There is no known exploitation of CVE-2026-130874 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130874 is a high-severity vulnerability in seerr-team Seerr, published on 17 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130874 in the wild and no public exploit code.

Affected packages and fixed versions:
- seerr-team/seerr (GitHub): affected all versions; fixed in 3.5.2

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-130874/ (Markdown: https://insights.sbomify.com/CVE-2026-130874/index.md)
```

## Sources

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

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