# CVE-2026-28416: Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing

> Attackers can force victim servers to make arbitrary HTTP requests via malicious Gradio Space configs, exposing internal services and cloud metadata.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-jmh7-g254-2cq9, PYSEC-2026-66

## What is CVE-2026-28416?

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

### Official description

Gradio is an open-source Python package designed for quick prototyping. Prior to version 6.6.0, a Server-Side Request Forgery (SSRF) vulnerability in Gradio allows an attacker to make arbitrary HTTP requests from a victim's server by hosting a malicious Gradio Space. When a victim application uses `gr.load()` to load an attacker-controlled Space, the malicious `proxy_url` from the config is trusted and added to the allowlist, enabling the attacker to access internal services, cloud metadata endpoints, and private networks through the victim's infrastructure. Version 6.6.0 fixes the issue.

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

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

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


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

Products: Gradio Project Gradio.

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

Upgrade gradio to 6.6.0 or later.

## Is CVE-2026-28416 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28416 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-2026-28416 and fix it if it is affected.

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

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 6.6.0
- gradio (PyPI): affected all versions; fixed in 6.6.0
- gradio (PyPI): affected all versions; fixed in 6.6.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-2026-28416/ (Markdown: https://insights.sbomify.com/CVE-2026-28416/index.md)
```

## Sources

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

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