Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-28414: 3.06% estimated exploitation activity in the next 30 days; percentile 87.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details 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. PoC Impact Arbitrary file read in the context of the Windows user running Gradio.

Published by the source

1 Mar 2026, 01:28 UTC

Last modified by the source

6 Jun 2026, 00:30 UTC

Source last checked

26 Oct 2026, 13:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-39mp-8hj3-5c49

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-39mp-8hj3-5c49

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-28414

Advisory: Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+
IDs: CVE-2026-28414, GHSA-39mp-8hj3-5c49
Record: https://patchnext.com/advisories/cve-2026-28414 (revision 2, source checked 26 Oct 2026, 13:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gradio 6.7.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gradio: affected < 6.7.0; fixed in 6.7.0

## Suggested inspection (read-only)
- `python -m pip show gradio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gradio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-39mp-8hj3-5c49 (OSV record GHSA-39mp-8hj3-5c49 lists affected ranges: PyPI gradio >=0 <6.7.0 (fixed))
- Verified: https://github.com/advisories/GHSA-39mp-8hj3-5c49 (GitHub-reviewed advisory GHSA-39mp-8hj3-5c49 lists affected ranges: PyPI gradio >=0 <6.7.0)

Commands are suggestions: review each one before running it.