Skip to content
Fencer Vulns
high 8.1

CVE-2024-47515 json

Pagure: generate_archive() follows symbolic links in temporary clones

published 2024-12-24 22 mo ago modified 2026-06-17 4 mo ago also EUVD-2024-42713

cvss
8.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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.

Patch / fix

  • pagure Debian 13 5.14.1+dfsg-1

debian advisories DEBIAN-CVE-2024-47515

  • pagure Ubuntu 22.04 LTS 5.11.3+dfsg-1ubuntu0.1
  • pagure Ubuntu 24.04 LTS 5.11.3+dfsg-2.1ubuntu0.2
  • pagure Ubuntu Pro 20.04 LTS 5.8.1+dfsg-3ubuntu0.1~esm1

ubuntu advisories UBUNTU-CVE-2024-47515

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-47515 updated cvss 8.1

pagure: generate_archive() follows symbolic links in temporary clones

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
22 mo ago

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Classification

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

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.