Quick answers
- Is CVE-2024-34511 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-34511 being exploited in the wild.
- How severe is CVE-2024-34511?
- Low severity, with a CVSS score of 3.1, published 7 July 2026.
- Which products and versions are affected?
- gradio (PyPI) ECOSYSTEM:introduced=0,fixed=4.13.0.
- Is there a fix for CVE-2024-34511?
- Yes. gradio (PyPI): upgrade to 4.13.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-34511 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2024-34511?
- Check whether you run gradio (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- gradio (PyPI): upgrade to 4.13.0 or later
pip install "gradio>=4.13.0"
Technical details
The vulnerability exists in Gradio's Component Server (versions before 4.13.0) due to improper consideration of the `_is_server_fn` flag when processing functions. This flag is intended to control which functions are eligible for remote execution. An unauthenticated attacker on the network can send crafted requests to the Component Server that bypass this validation check. By doing so, they can invoke functions that were not intended to be exposed as server functions, potentially leading to unauthorized code execution or information disclosure. The fix was implemented in version 4.13.0.
Affected products
- Gradio Gradio before 4.13.0
Identifiers
- CVE-2024-34511
- GHSA-34rf-p3r3-58x2
- PYSEC-2026-1407
Timeline
- 2024-05-05: disclosed: Vulnerability published on OSV
- 2024-05-05: patched: Fixed in version 4.13.0