# CVE-2024-51751: Arbitrary file read with File and UploadButton components in Gradio

> Attackers can read arbitrary files from the server by abusing File or UploadButton components in Gradio applications.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** GHSA-rhm9-gp5p-5248, PYSEC-2024-275

## What is CVE-2024-51751?

CVE-2024-51751 is a medium-severity path traversal vulnerability in Gradio Project Gradio, published on 6 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gradio is an open-source Python package designed to enable quick builds of a demo or web application. If File or UploadButton components are used as a part of Gradio application to preview file content, an attacker with access to the application might abuse these components to read arbitrary files from the application server. This issue has been addressed in release version 5.5.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

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

## Which versions are affected by CVE-2024-51751?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | From 5.0.0 | 5.5.0 |
| `gradio` | PyPI | From 5.0.0 | 5.5.0 |
| `gradio` | PyPI | From 5.0.0 | 5.5.0 |

Products: Gradio Project Gradio.

## How do I fix CVE-2024-51751?

Upgrade gradio to 5.5.0 or later.

## Is CVE-2024-51751 being exploited?

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

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

What it is: CVE-2024-51751 is a medium-severity path traversal vulnerability in Gradio Project Gradio, published on 6 Nov 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51751 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected from 5.0.0; fixed in 5.5.0
- gradio (PyPI): affected from 5.0.0; fixed in 5.5.0
- gradio (PyPI): affected from 5.0.0; fixed in 5.5.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-2024-51751/ (Markdown: https://insights.sbomify.com/CVE-2024-51751/index.md)
```

## Sources

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

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