# CVE-2021-29490: Unauthenticated GET requests through Remote Image endpoints

> Unauthenticated attackers can perform Server-Side Request Forgery via the imageUrl parameter, potentially accessing internal resources.

- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2021
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rgjw-4fwc-9v96

## What is CVE-2021-29490?

CVE-2021-29490 is a medium-severity server-side request forgery vulnerability in jellyfin, published on 5 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jellyfin is a free software media system that provides media from a dedicated server to end-user devices via multiple apps. Verions prior to 10.7.3 vulnerable to unauthenticated Server-Side Request Forgery (SSRF) attacks via the imageUrl parameter. This issue potentially exposes both internal and external HTTP servers or other resources available via HTTP `GET` that are visible from the Jellyfin server. The vulnerability is patched in version 10.7.3. As a workaround, disable external access to the API endpoints `/Items/*/RemoteImages/Download`, `/Items/RemoteSearch/Image` and `/Images/Remote` via reverse proxy, or limit to known-friendly IPs.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2021-29490?

It affects 1 product.


Products: Jellyfin Jellyfin.

## How do I fix CVE-2021-29490?

No fix has been published for CVE-2021-29490 yet. Limit exposure of the affected software until one is available.

## Is CVE-2021-29490 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-29490 exists.

Public exploit code:

- Jellyfin 10.7.2 - Server Side Request Forgery (nuclei): http/cves/2021/CVE-2021-29490.yaml

## Other vulnerabilities in jellyfin

- [CVE-2026-35031](https://insights.sbomify.com/CVE-2026-35031/): Jellyfin: Potential RCE via subtitle upload path traversal + .strm chain (critical 10.0)
- [CVE-2026-31852](https://insights.sbomify.com/CVE-2026-31852/): Jellyfin Possible Organization/Secret Compromise from dangerous CI implementation (critical 10.0)
- [CVE-2026-35033](https://insights.sbomify.com/CVE-2026-35033/): Jellyfin: Potential SSRF + Arbitrary file read via stream argument injection (critical 9.3)
- [CVE-2023-30627](https://insights.sbomify.com/CVE-2023-30627/): jellyfin-web has a stored cross-site scripting vulnerability in devices.js (critical 9.1)
- [CVE-2023-30626](https://insights.sbomify.com/CVE-2023-30626/): Jellyfin vulnerable to directory traversal and file write causing arbitrary code execution (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-29490 and fix it if it is affected.

What it is: CVE-2021-29490 is a medium-severity server-side request forgery vulnerability in jellyfin, published on 5 May 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-29490 exists.

Affected product: jellyfin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2021-29490/ (Markdown: https://insights.sbomify.com/CVE-2021-29490/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2021-29490
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-29490
- OSV: https://osv.dev/vulnerability/CVE-2021-29490

---
From sbomify Insights: https://insights.sbomify.com/CVE-2021-29490/
Summaries are generated and may contain mistakes; the official description above is the record.