Broken access control in Jellyfin session remote-control API
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- None · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · GHSA-4vx8-xhc9-qg6x. Fix status from GitHub. Impact type from CWE-639.
Summary
Jellyfin up to and including 12.0-RC5 lacks authorization checks on its session remote-control API. Any authenticated user who knows a target session ID can send popups, control playback and issue system commands to another user's client. Session IDs are MD5 hashes of the client name and device ID, so an attacker can compute them offline. The flaw is classified as an authorization bypass through a user-controlled key (CWE-639) and missing authorization (CWE-862).
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact AssertCanControl in SessionManager.cs only null-checks its arguments. It never verifies session ownership or the EnableRemoteControlOfOtherUsers permission. All the session remote-control endpoints are bare [Authorize], so any authenticated user who knows a target session ID can send popups, control playback, and issue system commands to another user's client. Session IDs are MD5(clientName + deviceId), so they can be computed offline rather than stolen. ### Patches _Has the problem been patched? What versions should users upgrade to?_ ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ ### References _Are there any links users can visit to find out more?_
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | jellyfin | <= 12.0-RC5 | 12.0 | Patch available | GHSA-4vx8-xhc9-qg6x |
- jellyfin Vendor— Affected <= 12.0-RC5 Fixed in 12.0 Patch available GHSA-4vx8-xhc9-qg6x
Remediation
Jellyfin 12.0 fixes this issue, so upgrade to version 12.0 or later.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-4vx8-xhc9-qg6x jellyfin Fixed in 12.0 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-4vx8-xhc9-qg6x
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences