CVE-2024-39236: Gradio · Code Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Until an official patch is released, organizations should implement strict network-level access controls to restrict access to Gradio interfaces, limiting exposure to trusted internal networks only. Employ application-layer firewalls or reverse proxies to filter and sanitize inputs before they reach the vulnerable component. Monitor logs and network traffic for unusual or suspicious activity indicative of code injection attempts. Consider running Gradio instances with the least privilege necessary and within isolated environments or containers to limit potential damage from exploitation. Regularly update and audit dependencies and monitor vendor communications for patches or mitigation updates. If possible, temporarily disable or restrict features related to /gradio/component_meta.py or avoid using version 4.36.1 until a fix is available. Conduct security assessments and penetration testing focused on injection vulnerabilities to identify and remediate similar risks.
Description
Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. This vulnerability is triggered via a crafted input. NOTE: the supplier disputes this because the report is about a user attacking himself.