Quick answers
- Is CVE-2026-48793 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48793 being exploited in the wild.
- How severe is CVE-2026-48793?
- High severity, with a CVSS score of 8.8, published 24 June 2026.
- Which products and versions are affected?
- Jellyfin < 10.11.10.
- Is there a fix for CVE-2026-48793?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-48793 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-48793?
- Check whether you run Jellyfin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An argument injection vulnerability exists in Jellyfin's subtitle conversion logic within SubtitleEncoder.ConvertTextSubtitleToSrtInternal. The application interpolates subtitle file paths into FFmpeg command-line arguments without proper normalization via EncodingUtils.NormalizePath(). On Linux systems, an attacker can use double-quote characters in filenames to break out of the intended argument quoting and inject arbitrary FFmpeg parameters. While the SubtitleController.GetSubtitle endpoint is reachable without authentication, the exploit requires the precondition of placing a malicious file into a directory scanned by the media library (e.g., via SMB, NFS, or guest uploads). Successful exploitation can lead to arbitrary file writes or information disclosure. The issue is resolved in version 10.11.10.
Affected products
- Jellyfin Jellyfin < 10.11.10
Timeline
- 2026-06-10: advisory: GitHub Security Advisory published
- 2026-06-24: disclosed: NVD publication date