# CVE-2024-1727: CSRF Vulnerability in gradio-app/gradio

> Attackers can exploit CSRF to upload large files to local Gradio servers, causing disk exhaustion and denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Mar 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-48cq-79qq-6f7x, PYSEC-2026-1409

## What is CVE-2024-1727?

CVE-2024-1727 is a medium-severity vulnerability in Gradio Project Gradio, published on 21 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability in gradio-app/gradio allows attackers to upload multiple large files to a victim's system if they are running Gradio locally. By crafting a malicious HTML page that triggers an unauthorized file upload to the victim's server, an attacker can deplete the system's disk space, potentially leading to a denial of service. This issue affects the file upload functionality as implemented in gradio/routes.py.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

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


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

Products: Gradio Project Gradio.

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

Upgrade gradio to 4.19.2 or later.

## Is CVE-2024-1727 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1727 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-1727 and fix it if it is affected.

What it is: CVE-2024-1727 is a medium-severity vulnerability in Gradio Project Gradio, published on 21 Mar 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1727 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 4.19.2
- gradio (PyPI): affected all versions; fixed in 4.19.2
- gradio (PyPI): affected all versions; fixed in 4.19.2

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-1727/ (Markdown: https://insights.sbomify.com/CVE-2024-1727/index.md)
```

## Sources

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

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