# CVE-2026-49119: Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess()

> Unauthenticated attackers can read arbitrary files outside the intended directory via path traversal in the FileExplorer component.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Jul 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-j36p-7w88-g82j, PYSEC-2026-2179

## What is CVE-2026-49119?

CVE-2026-49119 is a high-severity path traversal vulnerability in Gradio Project Gradio, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gradio before 6.16.0 contain a path traversal vulnerability in the FileExplorer component's preprocess() method that allows unauthenticated attackers to escape the configured root directory by supplying path segments containing directory traversal sequences or absolute paths. Attackers can provide crafted path segments that cause os.path.join to discard the root_dir prefix entirely, resulting in arbitrary file read or exposure of sensitive files outside the intended directory.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

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


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

Products: Gradio Project Gradio.

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

Upgrade gradio to 6.16.0 or later.

## Is CVE-2026-49119 being exploited?

There is no known exploitation of CVE-2026-49119 in the wild and no public exploit code.

## 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-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7)
- [CVE-2024-4325](https://insights.sbomify.com/CVE-2024-4325/): Server-Side Request Forgery (SSRF) in gradio-app/gradio (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-49119 and fix it if it is affected.

What it is: CVE-2026-49119 is a high-severity path traversal vulnerability in Gradio Project Gradio, published on 1 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-49119 in the wild and no public exploit code.

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

## Sources

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

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