How severe is GHSA-6qm2-wpxq-7qh2?

GHSA-6qm2-wpxq-7qh2 has a CVSS score of 8.6/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6qm2-wpxq-7qh2?

GHSA-6qm2-wpxq-7qh2 affects the following packages: gradio (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-6qm2-wpxq-7qh2?

Update gradio to 4.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qm2-wpxq-7qh2 is resolved across your whole dependency graph.

How do I detect GHSA-6qm2-wpxq-7qh2 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gradio. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-6qm2-wpxq-7qh2 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-6qm2-wpxq-7qh2?

O3 pinpoints whether GHSA-6qm2-wpxq-7qh2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6qm2-wpxq-7qh2 actively exploited in the wild?

No public exploit code has been indexed for GHSA-6qm2-wpxq-7qh2 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6qm2-wpxq-7qh2?

GHSA-6qm2-wpxq-7qh2 has an EPSS (Exploit Prediction Scoring System) score of 2.3%, placing it in the 81th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is there exploit tooling available for GHSA-6qm2-wpxq-7qh2?

A Nuclei detection template exists for GHSA-6qm2-wpxq-7qh2, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was GHSA-6qm2-wpxq-7qh2 published, and has it been updated?

GHSA-6qm2-wpxq-7qh2 was published on December 21, 2023 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-6qm2-wpxq-7qh2

HIGH

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

Also known asCVE-2023-51449PYSEC-2023-249

Published

Dec 21, 2023

Updated

Feb 16, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

2.3%probability of exploitation in next 30 days

Lower Risk81th percentile-79.21%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐍gradio

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Older versions of gradio contained a vulnerability in the /file route which made them susceptible to file traversal attacks in which an attacker could access arbitrary files on a machine running a Gradio app with a public URL (e.g. if the demo was created with share=True, or on Hugging Face Spaces) if they knew the path of files to look for.

This was not possible through regular URLs passed into a browser, but it was possible through the use of programmatic tools such as curl with the --pass-as-is flag.

Furthermore, the /file route in Gradio apps also contained a vulnerability that made it possible to use it for SSRF attacks.

Both of these vulnerabilities have been fixed in gradio==4.11.0

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`gradio`	all versions	4.11.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for gradio. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update gradio to 4.11.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qm2-wpxq-7qh2 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-6qm2-wpxq-7qh2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-6qm2-wpxq-7qh2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Older versions of `gradio` contained a vulnerability in the `/file` route which made them susceptible to file traversal attacks in which an attacker could access arbitrary files on a machine running a Gradio app with a public URL (e.g. if the demo was created with `share=True`, or on Hugging Face Spaces) if they knew the path of files to look for. This was not possible through regular URLs passed into a browser, but it was possible through the use of programmatic tools such as `curl` with the `--pass-as-is` flag. Furthermore, the `/file` route in Gradio apps also contained a vulnerability

O3 Security · Impact-Aware SCA

Is GHSA-6qm2-wpxq-7qh2 in your dependencies?

O3 detects GHSA-6qm2-wpxq-7qh2 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works