Skip to main content
CVE-2024-4253VulnerabilityPublished Updated

CVE-2024-4253: gradio-app/gradio · Improper Neutralization of Special Elements used in an OS Command

Affects gradio-app/gradioSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.7% chance of exploitation in 30 days – higher than 77% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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.

What to do

Affected software

ProductAffectedFixed in
gradio-app gradio-app/gradioAffected
  • <=0.6.12
Fixed in–

AI-suggested

To mitigate this vulnerability, organizations should immediately review and sanitize all inputs derived from GitHub context variables in their workflows, especially those that are echoed or passed to shell commands. Avoid directly embedding untrusted data in shell commands without proper escaping or validation. Limit the scope and permissions of secrets such as GITHUB_TOKEN by using fine-grained personal access tokens or GitHub's least privilege token settings. Implement strict branch protection rules and require code reviews for pull requests to reduce the risk of malicious input. Consider isolating workflows that handle sensitive operations and secrets from those that process untrusted inputs. Monitor workflow runs for unusual activity or unexpected command executions. Update to patched versions of gradio-app/gradio once available, or temporarily disable vulnerable workflows if feasible. Employ security scanning tools that detect command injection patterns in CI/CD configurations. Finally, educate development teams about secure CI/CD practices and the risks of improper input handling in automated workflows.

Description

A command injection vulnerability exists in the gradio-app/gradio repository, specifically within the 'test-functional.yml' workflow. The vulnerability arises due to improper neutralization of special elements used in a command, allowing for unauthorized modification of the base repository or secrets exfiltration. The issue affects versions up to and including '@gradio/video@0.6.12'. The flaw is present in the workflow's handling of GitHub context information, where it echoes the full name of the head repository, the head branch, and the workflow reference without adequate sanitization. This could potentially lead to the exfiltration of sensitive secrets such as 'GITHUB_TOKEN', 'COMMENT_TOKEN', and 'CHROMATIC_PROJECT_TOKEN'.

References

Community reviews

Loading reviews…