Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

CVE-2022-35909

HIGH

CVE-2022-35909 is a high-severity (CVSS 8.8) vulnerability in Jellyfin.Common. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2022-35909 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Incorrect Access Control and Cross Site Scripting in Jellyfin

Also known asGHSA-qwp3-5fw3-5wgv
Published
Aug 19, 2022
Updated
Jul 15, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
1 known

Blast Radius

1 pkg affected
.NETJellyfin.Common

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

In Jellyfin before 10.8, the /users endpoint has incorrect access control for admin functionality.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetJellyfin.Commonall versions10.8.0
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Jellyfin.Common. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Jellyfin.Common to 10.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-35909 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2022-35909 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2022-35909. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In Jellyfin before 10.8, the /users endpoint has incorrect access control for admin functionality.
O3 Security · Impact-Aware SCA

Is CVE-2022-35909 in your dependencies?

O3 detects CVE-2022-35909 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.