# CVE-2024-47515: Pagure: generate_archive() follows symbolic links in temporary clones

> A malicious user can exploit symbolic link handling in archive generation to disclose local files on the Pagure server.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2024
- **Updated:** 12 Aug 2025
- **Also known as:** DEBIAN-CVE-2024-47515, GHSA-jc9g-44f2-xqh4, UBUNTU-CVE-2024-47515

## What is CVE-2024-47515?

CVE-2024-47515 is a high-severity path traversal vulnerability, published on 24 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Pagure. Support of symbolic links during repository archiving of repositories allows the disclosure of local files. This flaw allows a malicious user to take advantage of the Pagure instance.

Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following)

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


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

Apply the vendor's patch.

## Is CVE-2024-47515 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47515 is a high-severity path traversal vulnerability, published on 24 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47515 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-47515/ (Markdown: https://insights.sbomify.com/CVE-2024-47515/index.md)
```

## Sources

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

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