Is this vulnerability remotely exploitable over the internet?

Yes, if the Jellyfin instance is reachable and the attacker can obtain any authenticated user account, they can target the LiveTV tuner API over the network. However, successful exploitation also depends on what internal resources or local files the Jellyfin server can reach.

What level of access does an attacker need to exploit this issue?

The attacker needs an authenticated Jellyfin account with LiveTV management permissions. In vulnerable versions, this permission is often granted by default to newly created users, making low-friction account creation a significant factor.

What is the safest general fix pattern, independent of specific versions?

The safest pattern is to treat tuner configuration as an administrative function, strictly validate tuner URLs (scheme, host, and path), and ensure the server cannot freely reach sensitive local files or internal network services. Applying least privilege to the Jellyfin process and its network environment is crucial.

Severity:

HIGH RISK

(8.1)

Unvalidated Tuner URL Paths & SSRF (CWE-73, CWE-918) in Jellyfin LiveTV M3U Endpoint

CVE-2026-35032

Published:

Apr 14, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-74;CWE-89

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

Database Compromise and Data Integrity Loss

April 27, 2026

CWE-863

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Privilege Escalation and Unauthorized Session Control

April 27, 2026

Vulnerability Type

Category:

Server-Side Request Forgery and Insecure Resource Access

CWE:

CWE-73;CWE-918

Impact:

Server-Side Request Forgery with Local File Read and Privilege Escalation

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Server-Side Request Forgery and Insecure Resource Access

CWE:

CWE-73;CWE-918

Impact:

Server-Side Request Forgery with Local File Read and Privilege Escalation

Severity:

HIGH RISK

(8.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

START 14 DAYS FREE TRIAL

BOOK A DEMO

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Made with Love in San Francisco

355 Bryant St. San Francisco, CA 94107, USA

Ask AI for summary of CodeAnt

Unvalidated Tuner URL Paths & SSRF (CWE-73, CWE-918) in Jellyfin LiveTV M3U Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(7.3)

SQL Injection via Unsanitized ID Parameter (CWE-89) in Pharmacy Sales and Inventory System /ajax.php

HIGH RISK

HIGH

(8.5)

Incorrect Authorization (CWE-863) in OpenClaw chat.send Session Management

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare

Product

Pricing

Company

Legal

Developers

Compare