Jellyfin through 12.4 Authorization Bypass via GET /Items/Suggestions
Affects Jellyfin Server through 12.4 when GET /Items/Suggestions is called without a userId parameter, as tested on 12.2. The exposed user is an authenticated non-admin account with restricted library access.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Jellyfin through 12.4 contains an authorization bypass vulnerability in SuggestionsController.GetSuggestions that allows authenticated non-administrator users to bypass library and parental restrictions by omitting the userId parameter. Attackers can repeatedly call GET /Items/Suggestions without userId to enumerate restricted items, including IDs and server filesystem paths, and then stream them.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- jellyfin jellyfin
through 12.4
References 5
GitHub · jellyfin/jellyfin
abraxaslabs.tech
Questions about CVE-2026-119551
What does this mean?
The endpoint queries the library as a null user when no userId is supplied, so a restricted non-admin account can read filesystem paths and item IDs for libraries it is not assigned to.Source: abraxaslabs.tech
Am I affected, and how do I check?
Jellyfin versions through 12.4 are listed as affected, and the research post tested Jellyfin Server 12.2. The conditions are a request to GET /Items/Suggestions without a userId parameter and an account with restricted library access.Source: abraxaslabs.tech
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be stated from them. Check the installed Jellyfin Server version against the affected range through 12.4.Source: abraxaslabs.tech
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What if there's no patch?
The checked facts do not describe a workaround. The bypass depends on the GET /Items/Suggestions request being made without a userId parameter.Source: abraxaslabs.tech