CVE-2024-34510VulnerabilityPublished 5 May 2024Updated 19 Nov 2024

CVE-2024-34510: gradio · n/a

Affects gradioSource CVE Database V5

Not known to be exploited · CVSS 7.5 High : upgrade to 4.20 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 51% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 4.20

CVSS:3.1/AC:L/AV:N/A:N/C:H/I:N/PR:N/S:U/UI:N

Attack Complexity: Low
Attack Vector: Network
Availability: None
Confidentiality: High
Integrity: None
Privileges Required: None
Scope: Unchanged
User Interaction: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Availability: None: There is no impact to availability within the impacted component.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 May 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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade gradio to 4.20.

Affected software

Product	Affected	Fixed in
PyPIgradio`pkg:pypi/gradio`Other threats	Affected <4.20	Fixed in 4.20

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-34510, organizations should immediately upgrade Gradio to version 4.20 or later, where the vulnerability is addressed. If upgrading is not immediately feasible, implement network-level controls to restrict access to Gradio interfaces, especially from untrusted networks. Employ strict credential management practices, including rotating any credentials potentially exposed and enforcing least privilege principles. Monitor logs and network traffic for unusual access patterns that may indicate exploitation attempts. Additionally, consider isolating AI model deployment environments to limit the impact of potential credential leakage. Developers should review and sanitize all inputs and outputs rigorously to prevent improper encoding or escaping issues. Finally, maintain awareness of updates from Gradio maintainers and apply patches promptly once available.

Description

Gradio before 4.20 allows credential leakage on Windows.

Impact

The primary impact of CVE-2024-34510 is the unauthorized disclosure of sensitive credentials, which can lead to further compromise of systems and data confidentiality. Organizations using vulnerable versions of Gradio on Windows may face risks such as unauthorized access to AI model interfaces, data exfiltration, and potential lateral movement within networks if leaked credentials are reused. The vulnerability does not directly affect system integrity or availability but undermines trust in the confidentiality of deployed AI services. Exploitation requires no authentication or user interaction, increasing the likelihood of automated attacks. This can be particularly damaging for enterprises relying on Gradio for internal or customer-facing AI applications, as leaked credentials could facilitate broader attacks or data breaches. The absence of known exploits currently reduces immediate risk but does not eliminate the threat, especially as attackers often develop exploits following public disclosure. The impact is amplified in sectors with high reliance on AI technologies and sensitive data, such as finance, healthcare, and technology industries.

CWE-116Improper Encoding or Escaping of Output (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Implementation
Understand the context in which your data will be used and the encoding that will be expected. This is especially important when transmitting data between different components, or when generating outputs that can contain multiple encodings at the same time, such as web pages or multi-part mail messages.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
Query Parameterization (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.6 (opens in a new tab)
V14.4.4 (opens in a new tab)
V14.4.2 (opens in a new tab)
Attack patterns
Cross Zone Scripting (opens in a new tab)
User-Controlled Filename (opens in a new tab)
Web Server Logs Tampering (opens in a new tab)
AJAX Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 04:46 UTC

WeaknessesCWE-116

Technical details

References

Community reviews

Related threats