Low

Gradio's dropdown component pre-process step does not limit the values to those in the dropdown list

  • Disclosed: 10.10.2024
  • Updated: 11.10.2026 15:17

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.

Patches

Yes, this issue is addressed in gradio>=5.0. Please upgrade to the latest version to resolve the problem.

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.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Python (PyPI) gradio < 5.0.0 5.0.0

References

CVSS score 5.3/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Weakness (CWE)
-
Platform
Python (PyPI)
Package
gradio
Disclosed
10.10.2024
Updated
11.10.2026 15:17

Sources and licenses

OSV / GitHub Advisory Database - GHSA-26jh-r8g2-6fpr - CC BY 4.0

Vulnerability history: gradio

All published vulnerabilities of this package (Python (PyPI)), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (51) in the archive
Total entries
51
First → latest
12.2021 07.2026
Without a fix
13
Exploited in attacks
0

Severity breakdown

  • Critical 5
  • High 19
  • Medium 22
  • Low 5

Disclosures per year

  1. 2021: 1
  2. 2022: 1
  3. 2023: 5
  4. 2024: 28
  5. 2025: 9
  6. 2026: 7
Severity:
  1. High · 7.5 CVE-2024-8966 <= 5.22.0 no fix
  2. High · 7.5 CVE-2024-10624 >= 4.38.0, <= 5.0.0-beta.2 no fix
  3. High · 8.2 CVE-2024-10648 >= 4.0.0, <= 5.0.0b2 no fix
  4. High · 7.5 CVE-2024-10569 >= 4.0.0, <= 5.0.0b2 no fix
  5. Critical CVE-2025-23042 < 5.11.0 5.11.0
  6. High · 7.5 CVE-2024-47867 < 5.0.0 5.0.0
  7. Gradio's dropdown component pre-process step does not limit the values to those in the dropdown list this entry
    Low · 5.3 ghsa-26jh-r8g2-6fpr < 5.0.0 5.0.0
  8. High · 8.1 CVE-2024-1728 < 4.19.2 4.19.2
  9. High · 8.6 CVE-2024-4325 <= 4.36.0 no fix
  10. High · 7.5 CVE-2024-34510 < 4.20.0 4.20.0
  11. High · 7.5 CVE-2024-1561 < 4.13.0 4.13.0
  12. High · 7.3 CVE-2024-2206 < 4.18.0 4.18.0
  13. Critical · 8.3 CVE-2021-43831 < 2.5.0 2.5.0

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.