Advisory

GHSA-26jh-r8g2-6fpr

Also known as: None

Summary

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

Details

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.

Severity

Low Basis: The source's own band: LOW

Dates

Published
2024-10-10 22:11 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

gradio

PyPI · All systems

Affected

  • introduced 0, fixed 5.0.0 (ecosystem)

Fixed versions

5.0.0

Fix

  • Fixed version 5.0.0
    pip install --upgrade gradio==5.0.0

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences