# CVE-2024-1540: Command Injection in gradio-app/gradio via deploy+test-visual.yml workflow

> Attackers can execute unauthorized commands via GitHub Actions workflows, potentially modifying repositories or exfiltrating secrets.

- **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2024
- **Updated:** 21 Aug 2024

## What is CVE-2024-1540?

CVE-2024-1540 is a high-severity command injection vulnerability in Gradio Project Gradio, published on 27 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A command injection vulnerability exists in the deploy+test-visual.yml workflow of the gradio-app/gradio repository, due to improper neutralization of special elements used in a command. This vulnerability allows attackers to execute unauthorized commands, potentially leading to unauthorized modification of the base repository or secrets exfiltration. The issue arises from the unsafe handling of GitHub context information within a `run` operation, where expressions inside `${{ }}` are evaluated and substituted before script execution. Remediation involves setting untrusted input values to intermediate environment variables to prevent direct influence on script generation.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-1540?

It affects 1 product.


Products: Gradio Project Gradio.

## How do I fix CVE-2024-1540?

No fix has been published for CVE-2024-1540 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-1540 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1540 exists.

Public exploit code:

- Controlled security-research lab reproducing CVE-2024-1540 (GitHub Actions command injection in gradio-app/gradio deploy+test-visual.yml) — flattened snapshot of gradio-app/gradio @ f35f615e33a5dd90bfeb106b6f5dca689849fcef (github_poc): https://github.com/pvharmo2/gha-lab-8e9316151c

## Other vulnerabilities in Gradio Project Gradio

- [CVE-2024-39236](https://insights.sbomify.com/CVE-2024-39236/): Withdrawn Advisory: Gradio was discovered to contain a code injection vulnerability via the component /gradio/component_meta.py (critical 9.8)
- [CVE-2023-6572](https://insights.sbomify.com/CVE-2023-6572/): Command Injection in gradio-app/gradio (critical 9.6)
- [CVE-2022-24770](https://insights.sbomify.com/CVE-2022-24770/): Improper Neutralization of Formula Elements in a CSV File in Gradio Flagging (high 8.8)
- [CVE-2026-49119](https://insights.sbomify.com/CVE-2026-49119/): Gradio < 6.16.0 Path Traversal via FileExplorer.preprocess() (high 8.7)
- [CVE-2025-23042](https://insights.sbomify.com/CVE-2025-23042/): Gradio Blocked Path ACL Bypass Vulnerability (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1540 and fix it if it is affected.

What it is: CVE-2024-1540 is a high-severity command injection vulnerability in Gradio Project Gradio, published on 27 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1540 exists.

Affected product: Gradio Project Gradio. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-1540/ (Markdown: https://insights.sbomify.com/CVE-2024-1540/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-1540
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-1540
- OSV: https://osv.dev/vulnerability/CVE-2024-1540

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-1540/
Summaries are generated and may contain mistakes; the official description above is the record.