Local file inclusion in gradio

Exploitation

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

CVSS

7.5 · CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2024-4941: 0.83% estimated exploitation activity in the next 30 days; percentile 57.61 (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.

A local file inclusion vulnerability exists in the JSON component of gradio-app/gradio and was discovered in version 4.25. The vulnerability arises from improper input validation in the postprocess() function within gradio/components/jsoncomponent.py, where a user-controlled string is parsed as JSON. If the parsed JSON object contains a path key, the specified file is moved to a temporary directory, making it possible to retrieve it later via the /file=.. endpoint. This issue is due to the processingutils.movefilestocache() function traversing any object passed to it, looking for a dictionary with a path key, and then copying the specified file to a temporary directory. The vulnerability can be exploited by an attacker to read files on the remote system, posing a significant security risk.

Published by the source

6 Jun 2024, 18:30 UTC

Last modified by the source

16 Oct 2025, 07:59 UTC

Source last checked

26 Oct 2026, 13:30 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6v6g-j5fq-hpvw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6v6g-j5fq-hpvw

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

# Patch Next advisory brief: CVE-2024-4941

Advisory: Local file inclusion in gradio
IDs: CVE-2024-4941, GHSA-6v6g-j5fq-hpvw
Record: https://patchnext.com/advisories/cve-2024-4941 (revision 2, source checked 26 Oct 2026, 13:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: gradio 4.31.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI gradio: affected < 4.31.3; fixed in 4.31.3

## 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-6v6g-j5fq-hpvw (OSV record GHSA-6v6g-j5fq-hpvw lists affected ranges: PyPI gradio >=0 <4.31.3 (fixed))
- Verified: https://github.com/advisories/GHSA-6v6g-j5fq-hpvw (GitHub-reviewed advisory GHSA-6v6g-j5fq-hpvw lists affected ranges: PyPI gradio >=0 <4.31.3)

Commands are suggestions: review each one before running it.