# Gradio makes the \`/file\` secure against file traversal and server-side request forgery attacks

Advisory record · `GHSA-6qm2-wpxq-7qh2`

- **Identifiers:** `GHSA-6qm2-wpxq-7qh2` · `CVE-2023-51449` · `PYSEC-2023-249`
- **State:** Confirmed
- **Severity:** CVSS 5.6 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 21 Dec 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 21 Dec 2023, 18:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gradio` (PyPI): affected `<4.11.0`; fixed in `4.11.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Gradio (PyPI) versions before 4.11.0 have a flaw in the /file route that allows file traversal and server-side request forgery. An attacker who knows file paths on a Gradio app with a public URL, such as one created with share=True or hosted on Hugging Face Spaces, could read arbitrary files, and could also make the server send requests to other destinations. Upgrade to gradio 4.11.0 or later.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.6 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.28, the 98th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 20 Dec 2023, 21:34 UTC: [Published by the maintainers as a GitHub repository advisory](https://github.com/gradio-app/gradio/security/advisories/GHSA-6qm2-wpxq-7qh2)
- 31 Oct 2026, 14:36 UTC: First seen by agentprime
- 31 Oct 2026, 14:36 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-6qm2-wpxq-7qh2)

## Sources

- [GitHub Advisory Database: GHSA-6qm2-wpxq-7qh2](https://github.com/advisories/GHSA-6qm2-wpxq-7qh2)
- [OSV: GHSA-6qm2-wpxq-7qh2](https://osv.dev/vulnerability/GHSA-6qm2-wpxq-7qh2)
- <https://github.com/gradio-app/gradio/security/advisories/GHSA-6qm2-wpxq-7qh2>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-51449>
- <https://github.com/gradio-app/gradio/commit/1b9d4234d6c25ef250d882c7b90e1f4039ed2d76>
- <https://github.com/gradio-app/gradio/commit/7ba8c5da45b004edd12c0460be9222f5b5f5f055>
- <https://github.com/gradio-app/gradio>
- <https://github.com/pypa/advisory-database/tree/main/vulns/gradio/PYSEC-2023-249.yaml>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-6qm2-wpxq-7qh2>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-6qm2-wpxq-7qh2/>. Everything for agents: <https://agentprime.io/llms.txt>.
