# CVE-2025-48889: Gradio Allows Unauthorized File Copy via Path Manipulation

> Unauthenticated attackers can copy arbitrary server files to fill disk space, causing denial of service in Gradio applications.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** Yes
- **Published:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-8jw3-6x8j-v96g, PYSEC-2025-119

## What is CVE-2025-48889?

CVE-2025-48889 is a medium-severity path traversal vulnerability in Gradio Project Gradio, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Gradio is an open-source Python package that allows quick building of demos and web application for machine learning models, API, or any arbitrary Python function. Prior to version 5.31.0, an arbitrary file copy vulnerability in Gradio's flagging feature allows unauthenticated attackers to copy any readable file from the server's filesystem. While attackers can't read these copied files, they can cause DoS by copying large files (like /dev/urandom) to fill disk space. This issue has been patched in version 5.31.0.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-48889?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gradio` | PyPI | All versions | 5.31.0 |
| `gradio` | PyPI | All versions | 5.31.0 |
| `gradio` | PyPI | From 5.25.2 | 5.31.0 |

Products: Gradio Project Gradio.

## How do I fix CVE-2025-48889?

Upgrade gradio to 5.31.0 or later.

## Is CVE-2025-48889 being exploited?

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

What it is: CVE-2025-48889 is a medium-severity path traversal vulnerability in Gradio Project Gradio, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48889 exists.

Affected packages and fixed versions:
- gradio (PyPI): affected all versions; fixed in 5.31.0
- gradio (PyPI): affected all versions; fixed in 5.31.0
- gradio (PyPI): affected from 5.25.2; fixed in 5.31.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-2025-48889/ (Markdown: https://insights.sbomify.com/CVE-2025-48889/index.md)
```

## Sources

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

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