Is CVE-2026-28416 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-28416 being exploited in the wild.

How severe is CVE-2026-28416?

High severity, with a CVSS score of 8.2, published 1 March 2026.

Which products and versions are affected?

gradio (PyPI) < 6.6.0, ECOSYSTEM:introduced=0,fixed=6.6.0.

Is there a fix for CVE-2026-28416?

Yes. gradio (PyPI): upgrade to 6.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-28416 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-28416?

Check whether you run gradio (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-28416: Gradio SSRF via malicious proxy_url in gr.load

Q: Which products and versions are affected?

gradio (PyPI) < 6.6.0, ECOSYSTEM:introduced=0,fixed=6.6.0.

Q: Is there a fix for CVE-2026-28416?

Yes. gradio (PyPI): upgrade to 6.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-28416 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-28416?

Check whether you run gradio (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-28416 · Severity: high · CVSS 8.2 · Published 2026-03-01

Gradio, a popular library for building machine learning web interfaces, is vulnerable to a security flaw that allows attackers to trick a server into making unauthorized requests. By hosting a malicious 'Space' and convincing a user to load it, an attacker can gain access to sensitive internal services, private network data, or cloud credentials. This could lead to the theft of administrative keys or exposure of private internal databases.

Technologies: gradio (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-28416 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-28416 being exploited in the wild.
How severe is CVE-2026-28416?: High severity, with a CVSS score of 8.2, published 1 March 2026.
Which products and versions are affected?: gradio (PyPI) < 6.6.0, ECOSYSTEM:introduced=0,fixed=6.6.0.
Is there a fix for CVE-2026-28416?: Yes. gradio (PyPI): upgrade to 6.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-28416 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-28416?: Check whether you run gradio (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

gradio (PyPI): upgrade to 6.6.0 or later
```
pip install "gradio>=6.6.0"
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Gradio's 'gr.load()' function due to insufficient validation of the 'proxy_url' parameter in remote configuration files. When a Gradio application loads an external Space, the 'proxy_url' provided by the remote config is automatically added to an internal allowlist without verification. An attacker can provide a malicious configuration pointing to internal IP addresses or cloud metadata services (e.g., 169.254.169.254). Because Gradio's built-in '/proxy' route only performs host-based validation against this allowlist, an attacker can then use the victim's server as a reverse proxy to access restricted internal endpoints. This vulnerability is patched in version 6.6.0.

Affected products

gradio-app gradio < 6.6.0

Identifiers

CVE-2026-28416
GHSA-jmh7-g254-2cq9
PYSEC-2026-66

Timeline

2026-02-27: disclosed
2026-02-27: patched: Fixed in version 6.6.0
2026-03-01: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.