Read the docs

Path traversal in Jellyfin lets attackers delete arbitrary folders

Priority MEDIUM 54CWE-22Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
None · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · GHSA-6828-c7cx-hvqm. Fix status from GitHub.

Summary

Jellyfin before 12.0 has a path traversal flaw (CWE-22) in its virtual folder endpoints, where the library name is joined to the library root without validation. Before the setup wizard is completed, an unauthenticated remote attacker can recursively delete or relocate any directory the server process can write, including the data directory and database. After setup, only an administrator can reach these endpoints.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

Description from the GitHub advisory

### Impact DELETE /Library/VirtualFolders and POST /Library/VirtualFolders/Name concatenate the caller-supplied library name onto the user-views root without validation, then pass the result to Directory.Delete(path, true) or Directory.Move. Because Path.Combine accepts a rooted second argument, the name escapes the library root either way: - name=.. → <data>/root, name=../.. → <data> - name=/var/lib/jellyfin/data → the root is discarded entirely This lets an attacker recursively delete or relocate any directory the server process can write, including the data directory and jellyfin.db. Impact is permanent data loss and denial of service. Before the startup wizard is completed, the FirstTimeSetupOrElevated policy grants anonymous access, so a freshly installed server reachable on the network can be destroyed without credentials. That is the primary risk. After setup, the endpoints require an administrator, who can already delete libraries — that variant is hardening only. POST /Library/VirtualFolders (add) is not affected; it sanitizes the name through IFileSystem.GetValidFilename. ### Patches _Has the problem been patched? What versions should users upgrade to?_ ### Workarounds - Complete the setup wizard immediately after installation, and keep a new server off untrusted networks until then — that is the unauthenticated window. - Block /Library/VirtualFolders at a reverse proxy until setup is complete. - Run the server as an unprivileged account limited to its own data and media directories. - Keep backups of the data directory. ### References _Are there any links users can visit to find out more?_

Why it matters now

Fix Fixed jellyfin: 12.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
—jellyfin< 12.012.0Patch availableGHSA-6828-c7cx-hvqm
  • jellyfin Vendor— Affected < 12.0 Fixed in 12.0 Patch available GHSA-6828-c7cx-hvqm

Remediation

Upgrade Jellyfin to version 12.0 or later. Until then, complete the setup wizard right after installation and block /Library/VirtualFolders at a reverse proxy.

Written with Claude Haiku 5.5 from the sources below · 2026-11-12

  • Fix · GHSA-6828-c7cx-hvqm jellyfin Fixed in 12.0 Advisory →

Timeline

  1. 2026-11-12 Threatist record created from GHSA-6828-c7cx-hvqm

References

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences