Gradio has a race condition in update_root_in_config may redirect user traffic
Published 10 Oct 2024 · Updated 21 Jan 2025
Is your project on an affected gradio?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <5.0.0
- Fixed in
- 5.0.0
pip install 'gradio>=5.0.0'Details
Impact
What kind of vulnerability is it? Who is impacted?
This vulnerability involves a race condition in the update_root_in_config function, allowing an attacker to modify the root URL used by the Gradio frontend to communicate with the backend. By exploiting this flaw, an attacker can redirect user traffic to a malicious server. This could lead to the interception of sensitive data such as authentication credentials or uploaded files. This impacts all users who connect to a Gradio server, especially those exposed to the internet, where malicious actors could exploit this race condition.
Patches
Yes, please upgrade to gradio>=5 to address this issue.
Is GHSA-xh2x-3mrm-fwqm in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected gradio, and gives you the command that fixes it.
More advisories for gradio
- HighCVE-2026-49119 Gradio FileExplorer preprocess path traversal allows files outside root_dir to reach callbacks · 1 Jul 2026
- LowCVE-2026-10783Gradio: Audio cache key ignores metadata when saving numpy audio outputs · 4 Jun 2026
- HighCVE-2026-48545Gradio contains a cookie injection vulnerability · 27 May 2026
- HighCVE-2026-28416Gradio has SSRF via Malicious `proxy_url` Injection in `gr.load()` Config Processing · 1 Mar 2026
- MediumCVE-2026-28415Gradio has an Open Redirect in its OAuth Flow · 1 Mar 2026
- HighCVE-2026-28414Gradio is Vulnerable to Absolute Path Traversal on Windows with Python 3.13+ · 1 Mar 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.