Gradio Allows Unauthorized File Copy via Path Manipulation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS

• CVE-2025-48889: 0.69% estimated exploitation activity in the next 30 days; percentile 52.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

An arbitrary file copy vulnerability in Gradio's flagging feature allows unauthenticated attackers to copy any readable file from the server's filesystem. While attackers can't read these copied files, they can cause DoS by copying large files (like /dev/urandom) to fill disk space. Description The flagging component doesn't properly validate file paths before copying files. Attackers can send specially crafted requests to the /gradioapi/run/predict endpoint to trigger these file copies. Source: User-controlled path parameter in the flagging functionality JSON payload Sink: shutil.copy operation in FileData.copytodir() method The vulnerable code flow: 1. A JSON payload is sent to the /gradioapi/run/predict endpoint 2. The path field within FileData object can reference any file on the system 3. When processing this request, the Component.flag() method creates a GradioDataModel object 4. The FileData.copytodir() method uses this path without proper validation: 5. The lack of…

Published by the source

29 May 2025, 22:36 UTC

Last modified by the source

5 Jun 2026, 18:00 UTC

Source last checked

26 Oct 2026, 13:42 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8jw3-6x8j-v96g

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8jw3-6x8j-v96g

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

# Patch Next advisory brief: CVE-2025-48889

Advisory: Gradio Allows Unauthorized File Copy via Path Manipulation
IDs: CVE-2025-48889, GHSA-8jw3-6x8j-v96g
Record: https://patchnext.com/advisories/cve-2025-48889 (revision 2, 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 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gradio 5.31.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gradio: affected < 5.31.0; fixed in 5.31.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-8jw3-6x8j-v96g (OSV record GHSA-8jw3-6x8j-v96g lists affected ranges: PyPI gradio >=0 <5.31.0 (fixed))
- Verified: https://github.com/advisories/GHSA-8jw3-6x8j-v96g (GitHub-reviewed advisory GHSA-8jw3-6x8j-v96g lists affected ranges: PyPI gradio >=0 <5.31.0)

Commands are suggestions: review each one before running it.