# CVE-2024-47516: Pagure: argument injection in pagurerepo.log()

> Attackers can achieve remote code execution on Pagure instances via argument injection in Git history retrieval.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2025
- **Updated:** 12 Aug 2025
- **Also known as:** DEBIAN-CVE-2024-47516, GHSA-cfhx-3wmq-q5rg, UBUNTU-CVE-2024-47516

## What is CVE-2024-47516?

CVE-2024-47516 is a critical command injection vulnerability, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in Pagure. An argument injection in Git during retrieval of the repository history leads to remote code execution on the Pagure instance.

Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command)

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


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

Apply the vendor's patch.

## Is CVE-2024-47516 being exploited?

There is no known exploitation of CVE-2024-47516 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47516 is a critical command injection vulnerability, published on 25 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47516 in the wild and no public exploit code.

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-47516/ (Markdown: https://insights.sbomify.com/CVE-2024-47516/index.md)
```

## Sources

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

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