# CVE-2026-35032: Jellyfin: Potential SSRF + Arbitrary file read via LiveTV M3U tuner

> Authenticated users can exploit SSRF and file read in the LiveTV tuner to exfiltrate the database and escalate privileges to admin.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/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:** 14 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-8fw7-f233-ffr8

## What is CVE-2026-35032?

CVE-2026-35032 is a high-severity server-side request forgery vulnerability in jellyfin, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jellyfin is an open source self hosted media server. Versions prior to 10.11.7 contain a vulnerability chain in the LiveTV M3U tuner endpoint (POST /LiveTv/TunerHosts), where the tuner URL is not validated, allowing local file read via non-HTTP paths and Server-Side Request Forgery (SSRF) via HTTP URLs. This is exploitable by any authenticated user because the EnableLiveTvManagement permission defaults to true for all new users. An attacker can chain these vulnerabilities by adding an M3U tuner pointing to an attacker-controlled server, serving a crafted M3U with a channel pointing to the Jellyfin database, exfiltrating the database to extract admin session tokens, and escalating to admin privileges. This issue has been fixed in version 10.11.7. If users are unable to upgrade immediately, they can disable Live TV Management privileges for all users.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-73 (External Control of File Name or Path)

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

It affects 1 product.


Products: Jellyfin Jellyfin.

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

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

## Is CVE-2026-35032 being exploited?

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

## Other vulnerabilities in jellyfin

- [CVE-2026-35031](https://insights.sbomify.com/CVE-2026-35031/): Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain (critical 10.0)
- [CVE-2026-31852](https://insights.sbomify.com/CVE-2026-31852/): Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation (critical 10.0)
- [CVE-2026-35033](https://insights.sbomify.com/CVE-2026-35033/): Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection (critical 9.3)
- [CVE-2023-30627](https://insights.sbomify.com/CVE-2023-30627/): jellyfin-web has a stored cross-site scripting vulnerability in devices.js (critical 9.1)
- [CVE-2023-30626](https://insights.sbomify.com/CVE-2023-30626/): Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-35032 is a high-severity server-side request forgery vulnerability in jellyfin, published on 14 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-35032 in the wild and no public exploit code.

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

## Sources

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

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