GHSA-26jh-r8g2-6fpr: Gradio Gradio's Dropdown Component Pre-process Step Vulnerability

LOW
Share
CVSS 5.3
Published
Advisory Summary

GHSA-26jh-r8g2-6fpr is a LOW (CVSS 5.3) gradio's dropdown component pre-process step vulnerability (General Security Weakness) affecting Gradio libraries in the PyPI ecosystem. The issue involves gradio's dropdown component pre-process step does not limit the values to those in the dropdown list. Remediation is available by upgrading affected packages to version 5.0.0.

GHSA-26jh-r8g2-6fpr at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-26jh-r8g2-6fpr
Severity LOW
CVSS v3.1 Base Score 5.3
CWE Classification General Security Weakness
Affected Product Gradio
Package Ecosystem PyPI
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix GHSA-26jh-r8g2-6fpr

To remediate this vulnerability, upgrade all affected Gradio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

gradio fixed: 5.0.0 
pip install gradio>=5.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show gradio

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-26jh-r8g2-6fpr, inspect your installed packages using pip:

pip show gradio

Analyze the terminal output to locate any version of Gradio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.0), your application is affected.

Note: The pip show gradio command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Gradio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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

GHSA-26jh-r8g2-6fpr Affected Gradio Versions

1 component(s)
Fixed Versions:
5.0.0
Product / Package Ecosystem Affected Versions Fixed Version
gradio
pypi/gradio
PyPI
< 5.0.0
5.0.0

References

GitHub Advisory / Wiki ADVISORY
https://github.com/gradio-app/gradio/security/advisories/GHSA-26jh-r8g2-6fpr
Gradio Source Repository REPOSITORY
https://github.com/gradio-app/gradio

Frequently Asked Questions

What is GHSA-26jh-r8g2-6fpr?
GHSA-26jh-r8g2-6fpr is a security vulnerability in Gradio involving Gradio's dropdown component pre-process step does not limit the values to those in the dropdown list under General Security Weakness.
Which Gradio versions are affected?
Affected versions include releases prior to 5.0.0 across affected packages: gradio.
What version fixes GHSA-26jh-r8g2-6fpr?
Upgrading to 5.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is gradio affected?
Yes, gradio is affected in releases prior to 5.0.0. Upgrade your dependency to 5.0.0 or later.
What is the CVSS score of GHSA-26jh-r8g2-6fpr?
GHSA-26jh-r8g2-6fpr has a CVSS v3.1 base score of 5.3 (LOW) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with GHSA-26jh-r8g2-6fpr?
GHSA-26jh-r8g2-6fpr is classified under General Security Weakness.
How can I check PyPI dependencies for GHSA-26jh-r8g2-6fpr?
Run the dependency tree command: 'pip show gradio'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-26jh-r8g2-6fpr",
  "modified" : "2024-10-10T22:11:29Z",
  "published" : "2024-10-10T22:11:29Z",
  "aliases" : [ ],
  "summary" : "Gradio's dropdown component pre-process step does not limit the values to those in the dropdown list",
  "details" : "### Impact\n**What kind of vulnerability is it? Who is impacted?**\n\nThis 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.\n\n### Patches\nYes, this issue is addressed in `gradio>=5.0`. Please upgrade to the latest version to resolve the problem.\n\n### Workarounds  \n**Is there a way for users to fix or remediate the vulnerability without upgrading?**\n\nTo 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" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N"
  }, {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:U"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "gradio"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "5.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/gradio-app/gradio/security/advisories/GHSA-26jh-r8g2-6fpr"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/gradio-app/gradio"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-10-10T22:11:29Z",
    "nvd_published_at" : null
  }
}