CVE-2022-35909 Incorrect Access Control and Cross Site Scripting in Jellyfin
Attackers can access admin functionality via the /users endpoint due to incorrect access control, potentially escalating privileges or modifying data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-35909?
CVE-2022-35909 is a high-severity missing authorization vulnerability in n/a, published on 19 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
In Jellyfin before 10.8, the /users endpoint has incorrect access control for admin functionality.
Which versions are affected by CVE-2022-35909?
2 open source packages ship an affected version, including Jellyfin.Common. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
Jellyfin.Common NuGet | All versions | 10.8.0 |
Jellyfin.Common NuGet | All versions | 10.8.0 |
Products include Jellyfin Jellyfin.
How do I fix CVE-2022-35909?
Upgrade Jellyfin.Common to 10.8.0 or later.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2022-35909 being exploited?
There is no known exploitation of CVE-2022-35909 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2026-35031 Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain
- CVE-2026-31852 Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation
- CVE-2026-35033 Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection
- CVE-2023-30627 jellyfin-web has a stored cross-site scripting vulnerability in devices.js
- CVE-2023-30626 Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution
Sources
Also known as GHSA-qwp3-5fw3-5wgv.