Is CVE-2026-35032 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-35032 being exploited in the wild.

How severe is CVE-2026-35032?

High severity, with a CVSS score of 8.1, published 14 April 2026.

Is there a fix for CVE-2026-35032?

A patch was published on 2023-03-31: Version 10.11.7 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-35032 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-35032?

Check whether you run Jellyfin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-35032: Jellyfin privilege escalation via SSRF and file read in LiveTV M3U tuner

CVE-2026-35032 · Severity: high · CVSS 8.1 · Published 2026-04-14

Jellyfin is an open-source media server used to manage and stream personal video and audio collections. A security flaw in the Live TV management feature allows any registered user to read sensitive files from the server or trick the server into making unauthorized network requests. In practice, an attacker can use this to steal the server's database, hijack administrator accounts, and take full control of the media server.

Technologies: Jellyfin. Vendors: Jellyfin.

Quick answers

Is CVE-2026-35032 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-35032 being exploited in the wild.
How severe is CVE-2026-35032?: High severity, with a CVSS score of 8.1, published 14 April 2026.
Which products and versions are affected?: Jellyfin < 10.11.7.
Is there a fix for CVE-2026-35032?: A patch was published on 2023-03-31: Version 10.11.7 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-35032 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-35032?: Check whether you run Jellyfin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A vulnerability chain exists in the LiveTV M3U tuner endpoint (POST /LiveTv/TunerHosts) due to insufficient validation of the tuner URL. In M3uParser.cs, the application fails to sanitize input before calling AsyncFile.OpenRead for non-HTTP paths (enabling local file read) or fetching HTTP URLs (enabling SSRF). Because the 'EnableLiveTvManagement' permission defaults to true for new users, any authenticated user can add a malicious M3U tuner. An attacker can point a channel to the 'jellyfin.db' file, stream it to exfiltrate the database, extract admin session tokens, and escalate their privileges to administrator. The issue is resolved in version 10.11.7 by improving endpoint sanitization and changing default user permissions.

Affected products

Jellyfin Jellyfin < 10.11.7

Timeline

2023-03-31: patched: Version 10.11.7 released
2026-04-14: advisory: GitHub Security Advisory published
2026-04-14: disclosed: CVE-2026-35032 published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.