Jellyfin through 12.4 SSRF via Gzip-Compressed Data URI in SVG Profile Images
Jellyfin through 12.4 rasterizes SVG profile images server-side using Svg.Skia library defaults, which resolve external references. Patched in 12.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 12.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Jellyfin through 12.4 contains a server-side request forgery vulnerability that lets authenticated users bypass SvgSecurityValidator by embedding gzip-compressed SVG in non-SVG image data URIs. Attackers can upload such profile images via POST /UserImage, then trigger unauthenticated rendering via GET /UserImage to fetch internal URLs, read local image files, or exhaust memory.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- jellyfin jellyfin
through 12.4
References 6
GitHub · jellyfin/jellyfin
abraxaslabs.tech
Questions about CVE-2026-119549
What does this mean?
SVG files accepted as user profile images can make the Jellyfin server fetch http:// and https:// references inside them. This can cause memory exhaustion (denial of service), server-side request forgery, and local file disclosure, where fetched responses that decode as images can be downloaded by the requester.Source: github.com
Am I affected, and how do I check?
Jellyfin versions through 12.4 are listed as affected, and SVG is an accepted image type for user profile images. To check, look at the installed Jellyfin server version and whether SVG is accepted for user images.Source: github.com
What should I do about it?
Upgrade Jellyfin to 12.0, the patched version listed in the advisory.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Why do the sources disagree?
The description says the vulnerability can be reached without authentication, but the CVSS vector lists privileges required as Low (PR:L). The sources do not reconcile these two statements.Source: github.com