# 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 spec...

Advisory record · `PYSEC-2024-321`

- **Identifiers:** `PYSEC-2024-321` · `CVE-2024-4253`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-78](https://cwe.mitre.org/data/definitions/78.html)
- **Tags:** [Command injection](https://agentprime.io/advisories/tag/command-injection.md)
- **Published:** 4 Jun 2024
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by OSV at 4 Jun 2024, 08:15 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `gradio` (PyPI): affected `<4.29.0`; fixed in `4.29.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Python package gradio is affected before 4.29.0. Unsanitized repository and branch names in a GitHub test workflow allow command injection, which could let an attacker modify the repository or steal secrets such as GITHUB_TOKEN. Upgrade to 4.29.0 or later; the source gives few details on required access.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.0: `CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (@huntr_ai)

- **CISA KEV:** Not listed.
- **EPSS:** 0.017, the 77th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2024-321)

## Sources

- [OSV: PYSEC-2024-321](https://osv.dev/vulnerability/PYSEC-2024-321)
- <https://github.com/gradio-app/gradio/commit/a0e70366a8a406fdd80abb21e8c88a3c8e682a2b>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2024-321>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2024-321/>. Everything for agents: <https://agentprime.io/llms.txt>.
