Summary
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
To mitigate the issue without upgrading, developers can add manual validation in their prediction function to check the received values against the allowed dropdown values before processing them.
Impact
What kind of vulnerability is it? Who is impacted?
This vulnerability is a data validation issue in the Gradio Dropdown component's pre-processing step. Even if the allow_custom_value parameter is set to False, attackers can bypass this restriction by sending custom requests with arbitrary values, effectively breaking the developer’s intended input constraints. While this alone is not a severe vulnerability, it can lead to more critical security issues, particularly when paired with other vulnerabilities like file downloads from the user's machine.
GHSA-26JH-R8G2-6FPR has a CVSS score of 5.3 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (5.0.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Yes, this issue is addressed in gradio>=5.0. Please upgrade to the latest version to resolve the problem.
Frequently Asked Questions
- What is GHSA-26JH-R8G2-6FPR? GHSA-26JH-R8G2-6FPR is a low-severity security vulnerability in gradio (pip), affecting versions < 5.0.0. It is fixed in 5.0.0.
- How severe is GHSA-26JH-R8G2-6FPR? GHSA-26JH-R8G2-6FPR has a CVSS score of 5.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of gradio are affected by GHSA-26JH-R8G2-6FPR? gradio (pip) versions < 5.0.0 is affected.
- Is there a fix for GHSA-26JH-R8G2-6FPR? Yes. GHSA-26JH-R8G2-6FPR is fixed in 5.0.0. Upgrade to this version or later.
- Is GHSA-26JH-R8G2-6FPR exploitable, and should I be worried? Whether GHSA-26JH-R8G2-6FPR is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-26JH-R8G2-6FPR is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-26JH-R8G2-6FPR? Upgrade
gradioto 5.0.0 or later.