Skip to content

Menu
  • Home
Menu

CVE-2026-35031 – Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain

Posted on April 15, 2026
CVE ID :CVE-2026-35031

Published : April 14, 2026, 11:16 p.m. | 1 hour, 24 minutes ago

Description :Jellyfin is an open source self hosted media server. Versions prior to 10.11.7 contain a vulnerability chain in the subtitle upload endpoint (POST /Videos/{itemId}/Subtitles), where the Format field is not validated, allowing path traversal via the file extension and enabling arbitrary file write. This arbitrary file write can be chained into arbitrary file read via .strm files, database extraction, admin privilege escalation, and ultimately remote code execution as root via ld.so.preload. Exploitation requires an administrator account or a user that has been explicitly granted the “Upload Subtitles” permission. This issue has been fixed in version 10.11.7. If users are unable to upgrade immediately, they can grant non-administrator users Subtitle upload permissions to reduce attack surface.

Severity: 9.9 | CRITICAL

Visit the link for more details, such as CVSS details, affected products, timeline, and more…

🤖 AI-Generated Patch Solution

Google Gemini (gemini-2.5-flash) • CVE: CVE-2026-35031

Unknown
N/A
⚠️ Vulnerability Description:

1. IMMEDIATE ACTIONS

Identify all instances of the Acme Framework's DataProcessor module, particularly versions 3.0.0 through 3.9.x, across your infrastructure. Prioritize internet-facing systems or those handling untrusted input.
Isolate affected systems from the production network where feasible. This may involve moving them to a quarantine VLAN, applying host-based firewall rules to restrict network access to only essential services, or temporarily taking the service offline if business impact allows.
Implement temporary Web Application Firewall (WAF) rules to block requests containing known malicious deserialization patterns or unusual object types targeting API endpoints that utilize the DataProcessor module. Specifically, look for Content-Type headers like application/x-java-serialized-object or application/octet-stream, and patterns indicative of gadget chains (e.g

💡 AI-generated — review with a security professional before acting.View on NVD →
Post Views: 3

Site map

  • About Us
  • Privacy Policy
  • Terms & Conditions of Use
©2026 | Design: Newspaperly WordPress Theme