# CVE-2026-10107: MoviePilot v2 SSRF via /api/v1/system/img/{proxy} Endpoint

> Authenticated attackers can exploit an image proxy endpoint to access internal network resources and exfiltrate data due to insufficient URL validation.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA: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:** 29 May 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-4hhq-38m9-mgg7

## What is CVE-2026-10107?

CVE-2026-10107 is a high-severity server-side request forgery vulnerability in jxxghp MoviePilot, published on 29 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MoviePilot v2 contains a server-side request forgery vulnerability in the image proxy endpoint that allows authenticated attackers to request arbitrary URLs by supplying a resource_token cookie and a URL whose domain matches the assembled allowlist. Attackers can bypass internal network protections because the SecurityUtils.is_safe_url function performs only domain-membership checking without blocking private, loopback, or link-local addresses, enabling enumeration of internal services such as Jellyfin, Emby, or Plex and exfiltration of data from internal network resources.

Weakness: CWE-918 (Server-Side Request Forgery)

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


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

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

## Is CVE-2026-10107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10107 is a high-severity server-side request forgery vulnerability in jxxghp MoviePilot, published on 29 May 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-10107 exists.

Affected product: jxxghp MoviePilot. 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-10107/ (Markdown: https://insights.sbomify.com/CVE-2026-10107/index.md)
```

## Sources

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

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