# CVE-2021-43831: Files on the host computer can be accessed from the Gradio interface

> Attackers can access arbitrary files on the host computer via Gradio interfaces due to unrestricted file paths, exposing sensitive data.


- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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:** 15 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-rhq2-3vr9-6mcr, PYSEC-2021-873

## What is CVE-2021-43831?

CVE-2021-43831 is a high-severity path traversal vulnerability in Gradio Project Gradio, published on 15 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Gradio is an open source framework for building interactive machine learning models and demos. In versions prior to 2.5.0 there is a vulnerability that affects anyone who creates and publicly shares Gradio interfaces. File paths are not restricted and users who receive a Gradio link can access any files on the host computer if they know the file names or file paths. This is limited only by the host operating system. Paths are opened in read only mode. The problem has been patched in gradio 2.5.0.

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

## Which versions are affected by CVE-2021-43831?

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


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

Products: Gradio Project Gradio.

## How do I fix CVE-2021-43831?

Upgrade gradio to 2.5.0 or later.

## Is CVE-2021-43831 being exploited?

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

Public exploit code:

- Gradio < 2.5.0 - Arbitrary File Read (nuclei): http/cves/2021/CVE-2021-43831.yaml

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

What it is: CVE-2021-43831 is a high-severity path traversal vulnerability in Gradio Project Gradio, published on 15 Dec 2021. 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-2021-43831 exists.

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

## Sources

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

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