# CVE-2026-119551: Jellyfin through 12.4 Authorization Bypass via GET /Items/Suggestions


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 4 Nov 2026
- **Also known as:** GHSA-72f8-2q8j-rxmr

## What is CVE-2026-119551?

CVE-2026-119551 is a high-severity vulnerability in jellyfin, published on 30 Oct 2026. 

### Official 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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-119551?


## How do I fix CVE-2026-119551?

No fix has been published for CVE-2026-119551 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-119551 being exploited?

There is no known exploitation of CVE-2026-119551 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-119551 and fix it if it is affected.

What it is: CVE-2026-119551 is a high-severity vulnerability in jellyfin, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-119551 in the wild and no public exploit code.

Affected product: jellyfin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-119551/ (Markdown: https://insights.sbomify.com/CVE-2026-119551/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-119551
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-119551
- OSV: https://osv.dev/vulnerability/CVE-2026-119551

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-119551/
Summaries are generated and may contain mistakes; the official description above is the record.