VulnerabilityPublished 24 Dec 2024Updated 12 Aug 2025

CVE-2024-47515: pagure · UNIX Symbolic Link (Symlink) Following

Affects pagureSource CVE Database V5

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
PyPIpagure`pkg:pypi/pagure`Other threats	Affected =5.14.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-47515, organizations should first upgrade Pagure to a version where this vulnerability is patched once available. In the absence of an immediate patch, administrators should implement strict access controls to limit repository creation and archiving privileges to trusted users only. Review and sanitize repositories for suspicious symbolic links before archiving. Consider disabling or restricting the archiving feature temporarily if feasible. Employ file system monitoring to detect unusual symlink activity or unexpected file access patterns. Additionally, containerizing or sandboxing Pagure instances can reduce the risk of local file exposure. Regularly audit server configurations and logs for signs of exploitation attempts. Educate developers and users about the risks of including symlinks in repositories. Finally, maintain an incident response plan to quickly address any suspected data leakage stemming from this vulnerability.

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.

Impact

The primary impact of CVE-2024-47515 is the unauthorized disclosure of local files on servers running vulnerable versions of Pagure. This can lead to exposure of sensitive information such as configuration files, credentials, private keys, or proprietary source code. Such data leakage can facilitate further attacks, including privilege escalation, lateral movement, or intellectual property theft. The integrity of repository archives is also compromised, as malicious actors can manipulate archive contents via symlinks. Organizations relying on Pagure for source code management, especially those hosting private or sensitive projects, face increased risk of data breaches. Since the vulnerability requires some level of privilege, insider threats or compromised accounts could exploit this flaw to escalate damage. The lack of known exploits in the wild suggests a window for proactive mitigation, but the high CVSS score underscores the urgency. The impact is especially critical for organizations in sectors with stringent data protection requirements, such as finance, government, and technology.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Feb 2026, 08:49 UTC

Technical details

References

Community reviews

Related threats