# CVE-2024-4254: Secrets Exfiltration in gradio-app/gradio

> Attackers can exfiltrate sensitive secrets like AWS keys and tokens by exploiting unsafe GitHub Actions workflow configurations in the Gradio repository.

- **Severity:** High 7.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Jun 2024
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-fc78-c36r-cc59

## What is CVE-2024-4254?

CVE-2024-4254 is a high-severity vulnerability in Gradio Project Gradio, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The 'deploy-website.yml' workflow in the gradio-app/gradio repository, specifically in the 'main' branch, is vulnerable to secrets exfiltration due to improper authorization. The vulnerability arises from the workflow's explicit checkout and execution of code from a fork, which is unsafe as it allows the running of untrusted code in an environment with access to push to the base repository and access secrets. This flaw could lead to the exfiltration of sensitive secrets such as GITHUB_TOKEN, HF_TOKEN, VERCEL_ORG_ID, VERCEL_PROJECT_ID, COMMENT_TOKEN, AWSACCESSKEYID, AWSSECRETKEY, and VERCEL_TOKEN. The vulnerability is present in the workflow file located at https://github.com/gradio-app/gradio/blob/72f4ca88ab569aae47941b3fb0609e57f2e13a27/.github/workflows/deploy-website.yml.

Weakness: CWE-214 (Invocation of Process Using Visible Sensitive Information)

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

It affects 1 product.


Products: Gradio Project Gradio.

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

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

## Is CVE-2024-4254 being exploited?

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

Public exploit code:

- Security-research lab: controlled reproduction of CVE-2024-4254 (GHSA-fc78-c36r-cc59) — deploy-website.yml fork checkout/code execution in gradio-app/gradio @ d4c503a (github_poc): https://github.com/pvharmo2/gha-lab-40e23db109

## 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-4254 and fix it if it is affected.

What it is: CVE-2024-4254 is a high-severity vulnerability in Gradio Project Gradio, published on 4 Jun 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-4254 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-4254/ (Markdown: https://insights.sbomify.com/CVE-2024-4254/index.md)
```

## Sources

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

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