CVE-2026-119549

Jellyfin through 12.4 SSRF via Gzip-Compressed Data URI in SVG Profile Images

Published Oct 30, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

Jellyfin up to and including version 12.4 suffers from a server‑side request forgery flaw that allows an authenticated user to upload a profile image containing a Gzip‑compressed SVG encoded as a data URI. Because the SvgSecurityValidator is bypassed, the image is rendered when a client performs an unauthenticated GET /UserImage request. The rendering engine then follows any URLs wrapped inside the SVG, enabling the attacker to cause the Jellyfin server to fetch internal network resources, read local image files, or exhaust server memory. The result is potential disclosure of internal data, local file access, or denial‑of‑service through resource exhaustion.

Affected Systems

Jellyfin servers running version 12.4 or earlier are vulnerable. The affected product is the Jellyfin media server, and the specific short CPE identifies all deployments of that product. Affected versions include all releases up to 12.4; no higher version has been confirmed safe in the current advisory.

Risk and Exploitability

The CVSS score of 7.1 classifies the issue as high severity. Although the EPSS score is not available, the flaw does not require sophisticated preparation; an attacker simply needs to be an authenticated user on the target server to upload the crafted image, and then an unauthenticated client can trigger the malicious rendering. The vulnerability is not listed in CISA KEV, suggesting that it has not yet been widely exploited in the wild, but the attack can succeed with minimal effort once authentication is obtained.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest Jellyfin release where this vulnerability is fixed.
  • Restrict GET /UserImage requests to authenticated users or block unauthenticated access.
  • Disable or whitelist image uploads to reject Gzip‑compressed SVG data URIs until a fix is applied.

Generated by OpenCVE AI on October 30, 2026 at 12:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
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.
Title Jellyfin through 12.4 SSRF via Gzip-Compressed Data URI in SVG Profile Images
First Time appeared Jellyfin
Jellyfin jellyfin
Weaknesses CWE-918
CPEs cpe:2.3:a:jellyfin:jellyfin:*:*:*:*:*:*:*:*
Vendors & Products Jellyfin
Jellyfin jellyfin
References
Metrics cvssV3_1

{'score': 7.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:H'}

cvssV4_0

{'score': 7.1, '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'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Oct 30, 2026, 4:11 PM
Reserved
Oct 30, 2026, 10:53 AM
Status
Awaiting Analysis
Published
Oct 30, 2026, 12:16 PM
Modified
Oct 30, 2026, 7:14 PM