Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

Gradio vulnerable to arbitrary file read with File and UploadButton components

CVE-2024-51751GHSA-rhm9-gp5p-5248

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (gradio 5.5.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • PyPI gradio

    Affected
    >= 5.0.0, < 5.5.0
    Fixed in
    5.5.0

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P · score source
EPSS
  • CVE-2024-51751: 0.68% estimated exploitation activity in the next 30 days; percentile 52.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary If File or UploadButton components are used as a part of Gradio application to preview file content, an attacker with access to the application might abuse these components to read arbitrary files from the application server. Details Consider the following application where a user can upload a file and preview its content: If we run this application and make the following request (which attempts to read the /etc/passwd file) Then this results in the following error on the server This is expected. However, if we now remove the "meta":{"type":"gradio.FileData"} from the request: This doesn't cause an error and results in the content of /etc/passwd being shown in the response! This works because Gradio relies on the processingutils.asyncmovefilestocache to sanitize all incoming file paths in all inputs. This function performs the following operation where clientutils.isfileobjwithmeta is used as a filter which tells on which inputs to perform the movetocache function (which also…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-rhm9-gp5p-5248

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-rhm9-gp5p-5248

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-51751

Advisory: Gradio vulnerable to arbitrary file read with File and UploadButton components
IDs: CVE-2024-51751, GHSA-rhm9-gp5p-5248
Record: https://patchnext.com/advisories/cve-2024-51751 (revision 3, source checked 26 Oct 2026, 13:42 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gradio 5.5.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gradio: affected >= 5.0.0, < 5.5.0; fixed in 5.5.0

## Suggested inspection (read-only)
- `python -m pip show gradio`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on gradio.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rhm9-gp5p-5248 (OSV record GHSA-rhm9-gp5p-5248 lists affected ranges: PyPI gradio >=5.0.0 <5.5.0 (fixed))
- Verified: https://github.com/advisories/GHSA-rhm9-gp5p-5248 (GitHub-reviewed advisory GHSA-rhm9-gp5p-5248 lists affected ranges: PyPI gradio >=5.0.0 <5.5.0)

Commands are suggestions: review each one before running it.

Loading voting…