High severity · published Jun 24, 2026
CVE-2026-49247
Jellyfin: Potential Authenticated path traversal in /ClientLog/Document
8.8
CVSS
0.5%
EPSS
No
On KEV
Description
Jellyfin is an open source self hosted media server. From 10.9.0 until 10.11.10, the POST /ClientLog/Document endpoint accepts the Authorization header's Client and Version fields and uses them unsanitized as components of the on-disk filename when persisting client-uploaded log documents. As a result, any authenticated non-admin user can include ../ sequences in the Client field to cause Jellyfin to write attacker-controlled content to arbitrary paths reachable by the Jellyfin service user, with a forced .log suffix. This vulnerability is fixed in 10.11.10.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
High
Integrity
High
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 46% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
JE
jellyfin · jellyfin
>= 10.9.0, < 10.11.10 · source: vendor
Affected product
JE
jellyfin
jellyfin
More from jellyfin
9.8
CVE-2026-31852
Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation
9.1
CVE-2026-35033
Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection
8.8
CVE-2026-48793
Jellyfin: Potential FFmpeg argument injection via unescaped subtitle file path
8.8
CVE-2026-35031
Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain
8.8
CVE-2025-31499
Jellyfin Vulnerable to Argument Injection in FFmpeg