How severe is GHSA-qh6x-j82h-vpf9?

GHSA-qh6x-j82h-vpf9 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qh6x-j82h-vpf9?

GHSA-qh6x-j82h-vpf9 affects the following packages: gradio (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-qh6x-j82h-vpf9?

Update gradio to 4.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qh6x-j82h-vpf9 is resolved across your whole dependency graph.

How do I detect GHSA-qh6x-j82h-vpf9 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-qh6x-j82h-vpf9 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-qh6x-j82h-vpf9?

O3 pinpoints whether GHSA-qh6x-j82h-vpf9 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-qh6x-j82h-vpf9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-qh6x-j82h-vpf9 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 type of vulnerability is GHSA-qh6x-j82h-vpf9?

GHSA-qh6x-j82h-vpf9 is classified as Open Redirect (CWE-601). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for GHSA-qh6x-j82h-vpf9?

A Nuclei detection template exists for GHSA-qh6x-j82h-vpf9, 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-qh6x-j82h-vpf9 published, and has it been updated?

GHSA-qh6x-j82h-vpf9 was published on April 16, 2024 and was last updated on July 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

MEDIUM severity

GHSA-qh6x-j82h-vpf9

MEDIUMFix: gradio-app/gradio@2ad3d9e

GHSA-qh6x-j82h-vpf9 is a medium-severity (CVSS 6.5) Open Redirect vulnerability in gradio. O3 Security confirms whether GHSA-qh6x-j82h-vpf9 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

gradio Server-Side Request Forgery vulnerability

Also known asCVE-2024-1183PYSEC-2026-1419

Published

Apr 16, 2024

Updated

Jul 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jul 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

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

An SSRF (Server-Side Request Forgery) vulnerability exists in the gradio-app/gradio repository, allowing attackers to scan and identify open ports within an internal network. By manipulating the 'file' parameter in a GET request, an attacker can discern the status of internal ports based on the presence of a 'Location' header or a 'File not allowed' error in the response.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`gradio`	all versions	4.10.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.10.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qh6x-j82h-vpf9 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-qh6x-j82h-vpf9 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-qh6x-j82h-vpf9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-qh6x-j82h-vpf9 in your dependencies?

O3 detects GHSA-qh6x-j82h-vpf9 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