Is CVE-2026-28414 exploited in the wild?

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

How severe is CVE-2026-28414?

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

Which products and versions are affected?

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

Is there a fix for CVE-2026-28414?

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

How is CVE-2026-28414 attacked?

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

Am I affected by CVE-2026-28414?

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-28414: Gradio absolute path traversal on Windows with Python 3.13+

Q: Which products and versions are affected?

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

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

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

Q: How is CVE-2026-28414 attacked?

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

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

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-28414 · Severity: high · CVSS 7.5 · Published 2026-03-01

Gradio, a popular library for building machine learning web interfaces, is vulnerable to a security flaw when running on Windows with Python 3.13 or newer. This vulnerability allows an attacker to bypass security restrictions and read sensitive files directly from the server's hard drive. This could lead to the exposure of private data, configuration files, or credentials, even if the application is configured to require a password.

Technologies: gradio (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-28414 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-28414 being exploited in the wild.
How severe is CVE-2026-28414?: High severity, with a CVSS score of 7.5, published 1 March 2026.
Which products and versions are affected?: gradio (PyPI) < 6.7.0, ECOSYSTEM:introduced=0,fixed=6.7.0.
Is there a fix for CVE-2026-28414?: Yes. gradio (PyPI): upgrade to 6.7.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-28414 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-28414?: 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.7.0 or later
```
pip install "gradio>=6.7.0"
```

Technical details

An absolute path traversal vulnerability exists in Gradio when deployed on Windows environments using Python 3.13+. The root cause is a change in Python 3.13's 'os.path.isabs' behavior, where root-relative paths (e.g., '/windows/win.ini') are no longer identified as absolute paths, causing Gradio's internal path-joining logic to fail its safety checks. An unauthenticated remote attacker can exploit this by sending specially crafted HTTP requests to the '/static/' endpoint to retrieve arbitrary files from the host operating system. The vulnerability is present even when authentication is enabled on the Gradio app. This issue is resolved in version 6.7.0.

Affected products

gradio-app gradio < 6.7.0

Identifiers

CVE-2026-28414
GHSA-39mp-8hj3-5c49
PYSEC-2026-64

Timeline

2026-02-27: disclosed
2026-03-01: advisory: GitHub Advisory published
2026-06-06: patched: Last updated/patch confirmed in version 6.7.0

References

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