Jellyfin Branding splash screen endpoint allows denial of service
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- —
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub.
Summary
Jellyfin up to and including 10.10.7 is affected. Requests with different, large dimensions bypass caching on the Branding splash screen endpoint, which lets an unauthenticated remote attacker make the server generate very large images. Repeated requests can exhaust disk space, memory and CPU until the server hangs or crashes. No code execution or similar effect is known.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
Description from the GitHub advisory
### Impact @whoopsi-daisy has reported a potential DoS vulnerability in Jellyfin. The Branding API endpoint allows an unauthenticated user to request a custom splash screen image with an arbitrary size. When sent repeatedly with different, large dimensions to a Jellyfin server, the requests will bypass caching and cause the server to generate multiple very large images, potentially impacting available disk space, memory, and CPU. With enough requests this can cause the target server to hang or crash. At this point there is no known possibility of code execution or other similar effects beyond slowdowns and potential crashes. ### Patches This issue has been fixed in versions 10.10.8 and the upcoming 10.11.0 (rc3 and newer). ### Workarounds Block access to the `/Branding/Splashscreen` endpoint in your reverse proxy. ### References N/A
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 | <=10.10.7 | 10.11.0 | Patch available | GHSA-rrr6-mvwg-9pg9 |
- jellyfin Vendor— Affected <=10.10.7 Fixed in 10.11.0 Patch available GHSA-rrr6-mvwg-9pg9
Remediation
Upgrade Jellyfin to version 10.10.8, or to 10.11.0 (rc3 and newer), which fix this issue. Until then, block access to the /Branding/Splashscreen endpoint in your reverse proxy.
Written with Claude Haiku 5.5 from the sources below · 2026-11-12
- Fix · GHSA-rrr6-mvwg-9pg9 jellyfin Fixed in 10.11.0 Advisory →
Timeline
- 2026-11-12 Threatist record created from GHSA-rrr6-mvwg-9pg9
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences