CVE-2026-49247
RCE via unsafe path handling in Jellyfin log upload endpoint.
Is CVE-2026-49247 being exploited?
Not confirmed. CVE-2026-49247 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.55% probability of exploitation in the next 30 days.
How severe is CVE-2026-49247?
CVE-2026-49247 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-49247?
Yes. A fix has been recorded for CVE-2026-49247. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49247 affect?
CVE-2026-49247 affects Jellyfin Media Server (versions < 10.11.10). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49247?
Upgrade to 10.11.10+ immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated non-admin can write attacker-controlled .log files to arbitrary server paths via path traversal, enabling RCE on the Jellyfin service.
Immediate action required
- affected>= 10.9.0 and < 10.11.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.