# CVE-2026-48793: Jellyfin: Potential FFmpeg argument injection via unescaped subtitle file path

> Unauthenticated attackers can inject FFmpeg arguments via malicious subtitle filenames, leading to arbitrary file writes and information disclosure.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** GHSA-wwwm-px48-fpvq

## What is CVE-2026-48793?

CVE-2026-48793 is a high-severity command injection vulnerability in jellyfin, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jellyfin is an open source self hosted media server. Prior to 10.11.10, a potential FFmpeg argument injection vulnerability exists in the subtitle conversion code path. SubtitleEncoder.ConvertTextSubtitleToSrtInternal (SubtitleEncoder.cs, line 382) interpolates the subtitle file path into FFmpeg command-line arguments without calling EncodingUtils.NormalizePath(). On Linux, filenames can contain double-quote characters, which break the argument quoting and allow injection of arbitrary FFmpeg arguments. The vulnerability is reachable without authentication via SubtitleController.GetSubtitle, which has no [Authorize] attribute. An attacker who can place a file in a Jellyfin media library directory (shared NAS, Samba share, guest upload) can achieve arbitrary file write on the server and information disclosure. This vulnerability is fixed in 10.11.10.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

## Which versions are affected by CVE-2026-48793?


## How do I fix CVE-2026-48793?

No fix has been published for CVE-2026-48793 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-48793 being exploited?

There is no known exploitation of CVE-2026-48793 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48793 and fix it if it is affected.

What it is: CVE-2026-48793 is a high-severity command injection vulnerability in jellyfin, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-48793 in the wild and no public exploit code.

Affected product: jellyfin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48793/ (Markdown: https://insights.sbomify.com/CVE-2026-48793/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48793
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48793
- OSV: https://osv.dev/vulnerability/CVE-2026-48793

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48793/
Summaries are generated and may contain mistakes; the official description above is the record.