Path traversal in Jellyfin HlsSegmentController exposes files
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-hw73-62vp-9gxf. Fix status from GitHub.
Summary
Jellyfin versions before 12.0 are affected. The request path in HlsSegmentController is not validated, so a crafted path can escape the transcode directory. An unauthenticated remote attacker can download arbitrary files through GetHlsPlaylistLegacy, and the audio and video segment endpoints have the same issue.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact The request path in HlsSegmentController is not validated to a valid path and could allow escaping the transcode path and downloading of any arbitrary file in GetHlsPlaylistLegacy . GetHlsAudioSegmentLegacy and GetHlsVideoSegmentLegacy have the same issue, and are NOT behind an Authorize so they are publicly exploitable. ### Patches _Has the problem been patched? What versions should users upgrade to?_ ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ ### References _Are there any links users can visit to find out more?_
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | jellyfin | < 12.0 | 12.0 | Patch available | GHSA-hw73-62vp-9gxf |
- jellyfin Vendor— Affected < 12.0 Fixed in 12.0 Patch available GHSA-hw73-62vp-9gxf
Remediation
Upgrade Jellyfin to version 12.0, the fixed version listed for the product.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-hw73-62vp-9gxf jellyfin Fixed in 12.0 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-hw73-62vp-9gxf
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences