NewApp Monitoring is liveSign up free
AgentbeamBeta
AI agent vulnerability · Gradio

CVE-2023-41626: Gradio arbitrary file upload vulnerability

mediumCVSS 3.1 4.8GHSA-v4q9-qgqf-7jwp

Gradio 3.27.0 has an arbitrary file upload flaw in its /upload interface that lets a remote client place files in the server's /tmp directory. The advisory data lists no patched version for the gradio package. Medium severity, with limited confidentiality and integrity impact.

Published Sep 16, 2023 · Updated Nov 12, 2023 · Analysis Nov 2, 2026

What an attacker can do

The /upload route of a Gradio app accepts files from clients. The public write-up, a short gist, says files can be uploaded to /tmp on the server, and that this could give an attacker unwanted access if other sites on the same server contain file-handling weaknesses. It gives no proof of concept, upload path details or exact conditions.

The CVSS 3.1 vector (AV:N, AC:H, PR:N, UI:N) shows a network attacker with no login, but with high attack complexity. It rates confidentiality and integrity impact as low and availability impact as none. That fits a flaw where the attacker can drop files but needs another weakness to turn them into something worse, such as a file inclusion bug in a neighbouring app.

Treat it as a foothold primitive, not a direct takeover. The sources do not describe what file types are accepted, nor whether the files can be executed or read back.

Who is affected

The pip package gradio at 3.27.0 and earlier, per the package data. The CVE text names only 3.27.0. Apps that are reachable over a network, with the default upload route enabled, are the exposed ones. Check:

pip show gradio

Also look in /tmp on the host for files you do not recognize.

gradio

Ecosystem
PyPI
Affected
<= 3.27.0
Fixed in
No patched version yet
Check
pip show gradio

How to fix it

The advisory data lists no patched version for gradio, and the two sources do not name a fixed release. Move to a current Gradio release, since later versions have changed their file handling, and check Gradio's own security advisories for the exact fix before relying on it. Until then, keep the app off untrusted networks or put authentication in front of it, run it in a container with a private /tmp, and do not share the host with other web apps. These steps are suggestions and not from the advisory.

How to tell if you were hit

List recent files in /tmp on the host that runs the Gradio app and compare them with expected temporary files. Check web server or Gradio access logs for POST requests to /upload from unfamiliar addresses, particularly with unusual file names or extensions. Look at other sites on the same host for new references to files in /tmp.

Original advisory

From the GitHub Advisory Database (CC BY 4.0).

Gradio v3.27.0 was discovered to contain an arbitrary file upload vulnerability via the /upload interface.

Questions

Is there a fixed version of Gradio for CVE-2023-41626?

The advisory data lists none. The gist and the entry name only 3.27.0 as affected. Check Gradio's own advisories for the release that changed the upload handling.

Does this give remote code execution?

The sources do not claim it. They describe a file upload into /tmp and an indirect risk if other sites on the server have file weaknesses.

Why is the severity only medium?

The CVSS vector has high attack complexity and only low confidentiality and integrity impact, with no availability impact.

Is it exploited in the wild?

The sources do not say so, and the entry has no CISA catalog data.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology

More Gradio vulnerabilities

All Gradio entries