CVE-2024-39236: Code injection vulnerability in Gradio component_meta.py
Gradio
Gradio contained a code injection vulnerability via crafted inputs, though the supplier disputed it as self-inflicted user attack vector. No real-world exploitation has been verified.
disclosed CVENo confirmed exploitation, so this record is tracked as a disclosed vulnerability and not counted as an incident. It moves into the counts if CISA or the vendor confirms exploitation. Why
- CVSS
- 9.8
- EPSS
- 0.01 · top 41% · 2026-11-13
- fix status
- Fix status unknown
- first report
- 1 Jul 2024
- last update
- 1 Jul 2024
- CVE ids
Timeline · 1
Sources · 1
Advisories and databases
- 2024-07-01CVE-2024-39236: Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py.NVD · nvd.nist.gov/vuln/detail/CVE-2024-39236
Titles and links belong to their publishers. The summary above is written by gcdRadar in its own words; data is CC BY-SA 4.0.
Classification
- lane
- Patch now
- AI role
- Attack on AI
- categories
- Infrastructure vulnerability
- severity
- 2 · Disclosed vulnerability
- fix status
- Fix status unknown
- targets
- Framework / tooling
- owasp llm top 10
- LLM03:2025 Supply Chain
- mitre atlas
- no technique for these categories
- tags
- code-injection
- dates
- happened 1 Jul 2024 · first reported 1 Jul 2024
- origin
- NVDVulnerability record from NVD / the GitHub Advisory Database. This product uses the NVD API but is not endorsed or certified by the NVD.
- record
- confidence 0.95 · created 2026-10-18 10:04Z · updated 2026-10-18 10:04Z
Lane, AI role, categories and severity come from the classifier; the OWASP and ATLAS rows are derived from the categories. How these are assigned
Copy a brief
This record as a short Markdown brief, for a ticket, a chat or a coding agent.
the brief as text
# CVE-2024-39236: Code injection vulnerability in Gradio component_meta.py https://gcdradar.vercel.app/incidents/cve-2024-39236-code-injection-vulnerability-in-gradio-compon · AIR-2024-0244 · closed 2024-07-01 - Lane: Patch now - Severity: 2 (Disclosed vulnerability) - Fix status: Fix status unknown - First reported: 2024-07-01 - AI role: Attack on AI - Products: Gradio - CVE ids: CVE-2024-39236 - CVSS: 9.8 ## Summary Gradio contained a code injection vulnerability via crafted inputs, though the supplier disputed it as self-inflicted user attack vector. No real-world exploitation has been verified. ## What to do No action recorded; read the sources below and the vendor's advisory. ## Latest updates - 2024-07-01: CVE-2024-39236: Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. (https://nvd.nist.gov/vuln/detail/CVE-2024-39236) ## Sources - 2024-07-01 NVD: CVE-2024-39236: Gradio v4.36.1 was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py. https://nvd.nist.gov/vuln/detail/CVE-2024-39236 Verify against the vendor's advisory before changing production. Data CC BY-SA 4.0, https://gcdradar.vercel.app.
Related
- closed8.6Gradio CVE-2024-4325: SSRF Vulnerability in Gradio
Patch now · Disclosed · since 6 Jun 2024 · CVE-2024-4325
AI - closed7.1Gradio CVE-2024-4254: Gradio Website Deployment Workflow Secrets Exfiltration
Patch now · Disclosed · since 4 Jun 2024 · CVE-2024-4254
AI - closed7.5Gradio CVE-2024-4253: Gradio Repository Workflow Command Injection Vulnerability
Patch now · Disclosed · since 4 Jun 2024 · CVE-2024-4253
AI - closed6.9Gradio CVE-2024-51751: Arbitrary file read vulnerability in Gradio components
Patch now · Disclosed · since 6 Nov 2024 · CVE-2024-51751
AI - closed7.5Gradio CVE-2024-47867: Gradio lacks FRP client integrity checking
Patch now · Disclosed · since 10 Oct 2024 · CVE-2024-47867
AI - closed6.9Gradio CVE-2024-47868: Gradio component post-processing file leaks
Patch now · Disclosed · since 10 Oct 2024 · CVE-2024-47868
AI