CVE-2024-0964 is a critical severity flaw (CVSS 9.4) in Gradio. The record links a Gradio commit and a huntr report but names no fixed version. This guide covers who is affected, how to check your exposure, and what to do now.
What's affected
The record lists Gradio with no version range.
The record gives a CVSS base score of 9.4 (Critical), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L. The record and the linked commit page do not clearly agree on what the fix was. The weakness class is CWE-22.
The record says a local file include could be triggered remotely through a user supplied JSON value in an API request, and scores it 9.4 Critical.
The record links a Gradio commit and a huntr report but names no fixed version. The commit page we fetched describes a client change titled "Fix api event drops", which does not obviously match a file include fix, so check the official Gradio advisory for the exact fixed release.
How to check if you're exposed
Run pip show gradio in each environment and compare with the version named in the Gradio security advisory. Search your inventory for apps built with Gradio, including notebooks and demo servers.
A free in-browser dependency scan at gold.safeguard.sh/scan can show whether a software package in your own projects matches this CVE, and the Gold directory entry for CVE-2024-0964 keeps the record details in one place. Reachability analysis helps you separate installations where the vulnerable code can actually be hit from those where it sits unused.
For hardware and appliances, no scanner will find them unless they are in an inventory, so start with a list of every device and application of this kind on your network.
What to do now
- Identify every instance of Gradio in your environment, including test and forgotten systems.
- Compare the version you found with the affected range above.
- Look for a fixed release from the vendor or project. The record links a Gradio commit and a huntr report but names no fixed version.
- Apply mitigations while you wait: upgrade Gradio to the latest release, do not expose demo apps to the internet without authentication, and run them as an unprivileged user with no access to sensitive files.
- Review logs around the affected component for unusual requests.
- Record the decision and a re-check date in your vulnerability tracker.
Why it matters
The weakness is path traversal and local file inclusion, CWE-22. A value in an API request decides which file the application reads, and the check on that value is not strict enough. An attacker can steer the application toward files outside the intended folder.
Gradio is often used to demo machine learning models, and those demos are frequently exposed for convenience. A demo server that holds API keys, model weights or cloud credentials on disk makes a file read more valuable than it first looks.
The record shows this CVE is not in the CISA Known Exploited Vulnerabilities catalog, and none of the pages used for this article report exploitation in the wild.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Should I expose a Gradio demo to the internet?
Only with authentication and with nothing sensitive readable by the process.
Where can I confirm the fixed version?
Check the vendor or project advisory first. The record links a Gradio commit and a huntr report but names no fixed version. This article is based on the NVD record and the pages listed under Sources.
Sources
- https://github.com/gradio-app/gradio/commit/d76bcaaaf0734aaf49a680f94ea9d4d22a602e70
- https://huntr.com/bounties/25e25501-5918-429c-8541-88832dfd3741
- Safeguard Gold record for CVE-2024-0964
Last reviewed: 19 October 2026.
