CVE-2026-49247

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Jellyfin is an open source self hosted media server. From 10.9.0 until 10.11.10, the POST /ClientLog/Document endpoint accepts the Authorization header's Client and Version fields and uses them unsanitized as components of the on-disk filename when persisting client-uploaded log documents. As a result, any authenticated non-admin user can include ../ sequences in the Client field to cause Jellyfin to write attacker-controlled content to arbitrary paths reachable by the Jellyfin service user, with a forced .log suffix. This vulnerability is fixed in 10.11.10.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
26.6%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 24, 2026
Patch available. Sources: github.
github Patch Available

Potential Authenticated path traversal in /ClientLog/Document · Advisory · jellyfin/jellyfin · GitHub

https://github.com/jellyfin/jellyfin/security/advisories/GHSA-jg92-mrxq-vv75

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 63× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:48 UTCEG score recompute
  3. 2026-07-15 04:02 UTCEG score recompute
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-14 15:15 UTCEG score recompute
  6. 2026-07-14 02:30 UTCEG score recompute
  7. 2026-07-13 22:30 UTCEPSS rescore
  8. 2026-07-13 13:44 UTCEG score recompute
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-13 00:58 UTCEG score recompute
  11. 2026-07-12 12:12 UTCEG score recompute
  12. 2026-07-12 05:46 UTCEPSS rescore
  13. 2026-07-11 23:26 UTCEG score recompute
  14. 2026-07-11 10:40 UTCEG score recompute
  15. 2026-07-11 08:27 UTCEPSS rescore
  16. 2026-07-10 21:54 UTCEG score recompute
  17. 2026-07-10 09:08 UTCEG score recompute
  18. 2026-07-09 20:17 UTCEG score recompute
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-09 07:30 UTCEG score recompute
  21. 2026-07-08 18:44 UTCEG score recompute
  22. 2026-07-08 15:16 UTCEPSS rescore
  23. 2026-07-08 05:56 UTCEG score recompute
  24. 2026-07-07 16:53 UTCEG score recompute
  25. 2026-07-07 13:46 UTCEPSS rescore
Show 38 more
  1. 2026-07-07 02:39 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 13:53 UTCEG score recompute
  4. 2026-07-06 02:23 UTCEPSS rescore
  5. 2026-07-06 01:06 UTCEG score recompute
  6. 2026-07-05 12:19 UTCEG score recompute
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 23:33 UTCEG score recompute
  9. 2026-07-04 10:46 UTCEG score recompute
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 21:54 UTCEG score recompute
  12. 2026-07-03 09:09 UTCEG score recompute
  13. 2026-07-02 20:22 UTCEG score recompute
  14. 2026-07-02 07:36 UTCEG score recompute
  15. 2026-07-01 18:50 UTCEG score recompute
  16. 2026-07-01 15:07 UTCEPSS rescore
  17. 2026-07-01 06:04 UTCEG score recompute
  18. 2026-06-30 23:22 UTCEPSS rescore
  19. 2026-06-30 17:16 UTCEG score recompute
  20. 2026-06-30 04:25 UTCEG score recompute
  21. 2026-06-29 15:38 UTCEG score recompute
  22. 2026-06-29 14:06 UTCEPSS rescore
  23. 2026-06-29 14:06 UTCEPSS rescore
  24. 2026-06-29 02:52 UTCEG score recompute
  25. 2026-06-28 14:07 UTCEPSS rescore
  26. 2026-06-28 14:06 UTCEG score recompute
  27. 2026-06-28 04:56 UTCEPSS rescore
  28. 2026-06-28 04:56 UTCEPSS rescore
  29. 2026-06-28 01:20 UTCEG score recompute
  30. 2026-06-27 12:33 UTCEG score recompute
  31. 2026-06-27 03:08 UTCEPSS rescore
  32. 2026-06-26 23:46 UTCEG score recompute
  33. 2026-06-26 11:00 UTCEG score recompute
  34. 2026-06-25 21:40 UTCEG score recompute
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-25 08:53 UTCEG score recompute
  37. 2026-06-24 20:06 UTCEG score recompute
  38. 2026-06-24 20:03 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49247?
CVE-2026-49247 is a high vulnerability published on June 24, 2026. Jellyfin is an open source self hosted media server. From 10.9.0 until 10.11.10, the POST /ClientLog/Document endpoint accepts the Authorization header's Client and Version fields and uses them unsanitized as components of the on-disk filename when persisting client-uploaded log documents. As a…
When was CVE-2026-49247 disclosed?
CVE-2026-49247 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49247 actively exploited?
CVE-2026-49247 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 26.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49247?
CVE-2026-49247 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-49247?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49247, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49247

Explore →

Is Your Infrastructure Affected by CVE-2026-49247?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs