# CVE-2026-59806: Gradio < 6.20.0 - Open Redirect and SSRF via /gradio_api/file= endpoint

> Attackers can exploit unvalidated URLs in Gradio to perform SSRF and retrieve sensitive cloud credentials or redirect users.

- **Severity:** Medium 4.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jul 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-rj25-5m4j-hcxq

## What is CVE-2026-59806?

CVE-2026-59806 is a medium-severity server-side request forgery vulnerability in gradio-app gradio, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Gradio before 6.20.0 contains an open redirect and server-side request forgery vulnerability that allows attackers to redirect users to arbitrary URLs or perform client-side SSRF by supplying unvalidated HTTP/HTTPS URLs to the file_fetch() function in the /gradio_api/file= endpoint. Attackers can craft a malicious FileData response targeting internal endpoints such as cloud metadata services to retrieve sensitive credentials including EC2 IAM role credentials.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-601 (URL Redirection to Untrusted Site)

## Which versions are affected by CVE-2026-59806?


## How do I fix CVE-2026-59806?

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

## Is CVE-2026-59806 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59806 and fix it if it is affected.

What it is: CVE-2026-59806 is a medium-severity server-side request forgery vulnerability in gradio-app gradio, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-59806 exists.

Affected product: gradio-app gradio. 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-2026-59806/ (Markdown: https://insights.sbomify.com/CVE-2026-59806/index.md)
```

## Sources

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

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