critical CVSS 9.1

CVE-2024-47871·Python vulnerability

Gradio is an open-source Python package designed for quick prototyping. This vulnerability involves **insecure communication** between the FRP (Fast Reverse Proxy) client and server when Gradio's `share=True` option is used. HTTPS is not enforced on the connection, allowing attackers to intercept and read files uploaded to the Gradio server, as well as modify responses or data sent between the client and server. This impacts users who are sharing Gradio demos publicly over the internet using `share=True` without proper encryption, exposing sensitive data to potential eavesdroppers. Users are advised to upgrade to `gradio>=5` to address this issue. As a workaround, users can avoid using `share=True` in production environments and instead host their Gradio applications on servers with HTTPS enabled to ensure secure communication.

Severity
critical
Software
Python
Fixed in
5.0.0
Published
2024-10-10

Affected versions

Until: 5.0.0

Fixed in: 5.0.0

How to fix this CVE

Upgrade Gradio to version 5.0.0 or later to enforce HTTPS encryption on FRP client-server communication. If you are currently using Gradio's `share=True` feature in production, immediately disable it and migrate to a self-hosted Gradio instance with proper TLS/SSL certificates. Users on older versions should patch as soon as possible to prevent unencrypted data transmission.

sudo dnf update python3 && pip3 install --upgrade gradio>=5.0.0

Defensia detects this vulnerability

How to check if you are affected

  1. Check installed Gradio version: pip3 show gradio | grep Version
  2. Verify if Gradio is actively used with share=True: grep -r 'share=True' /path/to/gradio/apps/ --include='*.py'
  3. Monitor network traffic for unencrypted FRP connections: tcpdump -i any 'tcp port 7860' -A | grep -i 'frp\|gradio'
  4. Confirm patch installation: pip3 show gradio | grep Version (should show 5.0.0 or higher)

FAQ

What is CVE-2024-47871?

CVE-2024-47871 is a critical vulnerability in Gradio where the FRP reverse proxy connection used by the `share=True` feature operates without HTTPS encryption, allowing attackers on the network path to intercept uploaded files and modify server responses.

Is CVE-2024-47871 being actively exploited?

No, CVE-2024-47871 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits have been released, but the critical CVSS score warrants immediate patching.

What versions of Gradio are affected by CVE-2024-47871?

All versions of Gradio prior to 5.0.0 are vulnerable when the `share=True` option is enabled. Version 5.0.0 and later enforce HTTPS on FRP communications.

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

Run `pip3 show gradio` to check the version number. If it is below 5.0.0 and you have `share=True` configured in any Gradio application, your deployment is vulnerable.

Does Defensia detect CVE-2024-47871?

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

Related Python CVEs

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-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-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-47871. Free for 1 server.

Get started free