# CVE-2026-28414: Gradio has Absolute Path Traversal on Windows with Python 3.13+


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 27 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-39mp-8hj3-5c49, PYSEC-2026-64

## What is CVE-2026-28414?

CVE-2026-28414 is a high-severity vulnerability in Gradio Project Gradio, published on 27 Feb 2026. 

### Official description

Gradio is an open-source Python package designed for quick prototyping. Prior to version 6.7, Gradio apps running on Window with Python 3.13+ are vulnerable to an absolute path traversal issue that enables unauthenticated attackers to read arbitrary files from the file system. Python 3.13+ changed the definition of `os.path.isabs` so that root-relative paths like `/windows/win.ini` on Windows are no longer considered absolute paths, resulting in a vulnerability in Gradio's logic for joining paths safely. This can be exploited by unauthenticated attackers to read arbitrary files from the Gradio server, even when Gradio is set up with authentication. Version 6.7 fixes the issue.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-36 (Absolute Path Traversal)

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

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


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

Products: Gradio Project Gradio.

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

Upgrade gradio to 6.7.0 or later.

## Is CVE-2026-28414 being exploited?

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

Public exploit code:

- Gradio - Absolute Path Traversal (nuclei): http/cves/2026/CVE-2026-28414.yaml

## 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-28414 and fix it if it is affected.

What it is: CVE-2026-28414 is a high-severity vulnerability in Gradio Project Gradio, published on 27 Feb 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28414 exists.

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

## Sources

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

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