medium CVSS 6.5

CVE-2024-51751·Python vulnerability

Gradio is an open-source Python package designed to enable quick builds of a demo or web application. 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. This issue has been addressed in release version 5.5.0 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Severity
medium
Software
Python
Fixed in
5.5.0
Published
2024-11-06

Affected versions

From: 5.0.0

Until: 5.5.0

Fixed in: 5.5.0

How to fix this CVE

Upgrade Gradio to version 5.5.0 or later to remediate the unauthorized file read vulnerability affecting File and UploadButton components. Organizations running Gradio versions 5.0.0 through 5.4.x should prioritize this update, as authenticated users can exploit these components to access sensitive files on the application server. No workarounds are available; patching is the only mitigation.

sudo dnf update python3-gradio || sudo pip3 install --upgrade gradio==5.5.0

Defensia detects this vulnerability

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Implement access controls on file preview endpoints by validating file paths against a whitelist of allowed directories. Reject any preview requests that attempt to traverse parent directories or reference paths outside the designated upload directory. Add authentication rate limiting to reduce the window for brute-force file enumeration attempts.

How to check if you are affected

  1. Check Gradio version: python3 -c "import gradio; print(gradio.__version__)"
  2. Identify Gradio applications in use: grep -r "gr.File\|gr.UploadButton" /path/to/app --include="*.py"
  3. Search application logs for suspicious file access patterns: grep -i "preview\|download\|file" /var/log/application.log | grep -v expected_users
  4. Verify patched version is running: python3 -c "import gradio; print(gradio.__version__)" and confirm version >= 5.5.0

FAQ

What is CVE-2024-51751?

This vulnerability allows authenticated users to bypass file access restrictions in Gradio's File and UploadButton components, enabling unauthorized reading of arbitrary files from the application server during file preview operations.

Is CVE-2024-51751 being actively exploited?

No, CVE-2024-51751 is not currently listed on the CISA Known Exploited Vulnerabilities catalog, and no public exploits are available. However, the vulnerability requires only authentication and low complexity to exploit.

What versions of Python are affected by CVE-2024-51751?

CVE-2024-51751 affects Gradio versions 5.0.0 through 5.4.x. The vulnerability is not tied to Python itself but to the Gradio package running on Python; it impacts any deployment using vulnerable Gradio versions regardless of Python version.

How do I check if my server is vulnerable to CVE-2024-51751?

Run `python3 -c "import gradio; print(gradio.__version__)"` and verify the version is 5.5.0 or later. If the output is 5.0.0-5.4.x, your deployment is vulnerable.

Does Defensia detect CVE-2024-51751?

Yes — Defensia's CVE advisory scanner compares installed Gradio package versions against the NVD database. If Gradio is installed on a monitored server, CVE-2024-51751 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2024-51751. Free for 1 server.

Get started free