# CVE-2024-2206: SSRF Vulnerability in gradio-app/gradio

> Attackers can exploit insufficient URL validation in Gradio's proxy route to access internal endpoints via Server-Side Request Forgery.

- **Severity:** High 7.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-r364-m2j9-mf4h, PYSEC-2026-1420

## What is CVE-2024-2206?

CVE-2024-2206 is a high-severity server-side request forgery vulnerability in Gradio Project Gradio, published on 27 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An SSRF vulnerability exists in the gradio-app/gradio due to insufficient validation of user-supplied URLs in the `/proxy` route. Attackers can exploit this vulnerability by manipulating the `self.replica_urls` set through the `X-Direct-Url` header in requests to the `/` and `/config` routes, allowing the addition of arbitrary URLs for proxying. This flaw enables unauthorized proxying of requests and potential access to internal endpoints within the Hugging Face space. The issue arises from the application's inadequate checking of safe URLs in the `build_proxy_request` function.

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

## Which versions are affected by CVE-2024-2206?

3 open source packages ship an affected version, including gradio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | All versions | 4.18.0 |
| `gradio` | PyPI | All versions | 4.18.0 |
| `gradio` | PyPI | All versions | 4.18.0 |

Products: Gradio Project Gradio.

## How do I fix CVE-2024-2206?

Upgrade gradio to 4.18.0 or later.

## Is CVE-2024-2206 being exploited?

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

## Other vulnerabilities in Gradio Project Gradio

- [CVE-2024-39236](https://insights.sbomify.com/CVE-2024-39236/): Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py (critical 9.8)
- [CVE-2023-6572](https://insights.sbomify.com/CVE-2023-6572/): Command Injection in gradio-app/gradio (critical 9.6)
- [CVE-2022-24770](https://insights.sbomify.com/CVE-2022-24770/): Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging (high 8.8)
- [CVE-2026-49119](https://insights.sbomify.com/CVE-2026-49119/): Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess() (high 8.7)
- [CVE-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2206 and fix it if it is affected.

What it is: CVE-2024-2206 is a high-severity server-side request forgery vulnerability in Gradio Project Gradio, published on 27 Mar 2024. 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-2024-2206 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 4.18.0
- gradio (PyPI): affected all versions; fixed in 4.18.0
- gradio (PyPI): affected all versions; fixed in 4.18.0

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-2024-2206/ (Markdown: https://insights.sbomify.com/CVE-2024-2206/index.md)
```

## Sources

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

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