---
id: GHSA-26jh-r8g2-6fpr
title: >-
  Gradio's dropdown component pre-process step does not limit the values to
  those in the dropdown list
summary: >-
  Gradio's dropdown component pre-process step does not limit the values to
  those in the dropdown list
severity: medium
cvss: 5.3
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N'
vendor: gradio
product: gradio
ecosystem: pip
affected:
  - gradio < 5.0.0
patched:
  - gradio 5.0.0
published: '2024-10-10'
updated: '2026-09-10'
sourceUpdated: '2026-09-10T03:50:19.171244086Z'
source: OSV
sourceUrl: 'https://osv.dev/vulnerability/GHSA-26jh-r8g2-6fpr'
references:
  - url: >-
      https://github.com/gradio-app/gradio/security/advisories/GHSA-26jh-r8g2-6fpr
  - url: 'https://github.com/gradio-app/gradio'
tags:
  - osv
  - pip
ingestedAt: '2026-09-12T03:13:01.633Z'
---

## Overview

### 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 packages

- `gradio < 5.0.0`

## Remediation

Upgrade to a patched release:

- `gradio 5.0.0`