CVE-2026-35031
Path Traversal and RCE in Jellyfin Subtitle Upload Endpoint
Publication date: 2026-04-14
Last updated on: 2026-04-23
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| jellyfin | jellyfin | to 10.11.7 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
| CWE-187 | The product performs a comparison that only examines a portion of a factor before determining whether there is a match, such as a substring, leading to resultant weaknesses. |
| CWE-20 | The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Jellyfin versions prior to 10.11.7 in the subtitle upload endpoint (POST /Videos/{itemId}/Subtitles). The Format field is not properly validated, which allows an attacker to perform path traversal through the file extension. This enables arbitrary file write on the server.
The arbitrary file write can be chained to arbitrary file read via .strm files, extraction of the database, escalation to administrator privileges, and ultimately remote code execution as root through manipulation of ld.so.preload.
Exploitation requires either an administrator account or a user explicitly granted the "Upload Subtitles" permission.
The issue was fixed in version 10.11.7. Users unable to upgrade immediately can reduce the attack surface by granting subtitle upload permissions only to non-administrator users.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Jellyfin to version 10.11.7 or later where the issue is fixed.
If immediate upgrade is not possible, reduce the attack surface by granting Subtitle upload permissions only to non-administrator users.
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized arbitrary file writes and reads on the server hosting Jellyfin.
An attacker can escalate privileges to administrator level and execute code remotely as the root user, potentially compromising the entire system.
Such exploitation could lead to data theft, system manipulation, service disruption, and full system compromise.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in Jellyfin allows arbitrary file write and remote code execution with root privileges, which can lead to unauthorized access and control over the system.
Such unauthorized access and potential data breaches could impact compliance with common standards and regulations like GDPR and HIPAA, which require protection of sensitive data and system integrity.
Exploitation requires an administrator or a user with explicit subtitle upload permissions, indicating that improper permission management could increase risk.
Fixing the vulnerability by upgrading to version 10.11.7 or restricting subtitle upload permissions can help reduce the attack surface and support compliance efforts.