Server-side Request Forgery (SSRF) Affecting jellyfin.data package, versions [,10.11.7)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Server-side Request Forgery (SSRF) vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-DOTNET-JELLYFINDATA-16068527
- published15 Apr 2026
- disclosed14 Apr 2026
- creditPiotr Niełacny, Gerhard Botha
Introduced: 14 Apr 2026
NewCVE-2026-35032 (opens in a new tab)How to fix?
Upgrade Jellyfin.Data to version 10.11.7 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the POST /LiveTv/TunerHosts endpoint when the tuner URL is not properly validated. An attacker can read arbitrary local files and perform unauthorized requests to internal or external systems by submitting a crafted M3U tuner configuration. This can lead to exfiltration of sensitive data, such as database files containing admin session tokens, and escalation of privileges. This is only exploitable if the user has the EnableLiveTvManagement permission, which defaults to true for all new users.