CVE-2024-32021
LOWDescription
Git is a revision control system. Prior to versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4, when cloning a local source repository that contains symlinks via the filesystem, Git may create hardlinks to arbitrary user-readable files on the same filesystem as the target repository in the `objects/` directory. Cloning a local repository over the filesystem may creating hardlinks to arbitrary user-owned files on the same filesystem in the target Git repository's `objects/` directory. When cloning a repository over the filesystem (without explicitly specifying the `file://` protocol or `--no-local`), the optimizations for local cloning will be used, which include attempting to hard link the object files instead of copying them. While the code includes checks against symbolic links in the source repository, which were added during the fix for CVE-2022-39253, these checks can still be raced because the hard link operation ultimately follows symlinks. If the object on the filesystem appears as a file during the check, and then a symlink during the operation, this will allow the adversary to bypass the check and create hardlinks in the destination objects directory to arbitrary, user-readable files. The problem has been patched in versions 2.45.1, 2.44.1, 2.43.4, 2.42.2, 2.41.1, 2.40.2, and 2.39.4.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:N/I:L/A:L
Exploit Intelligence
Moderate risk: more likely to be exploited than 60% of all known CVEs.
References
Related Vulnerabilities
Other CWE-547 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2019-14837 | Critical | 9.1 | 1.7% | - | Fix |
| CVE-2023-1712 | Critical | 9.8 | 0.8% | - | Fix |
| CVE-2025-30206 | Critical | 9.8 | 0.8% | - | - |
| CVE-2025-49151 | Unscored | - | 0.6% | - | - |
| CVE-2025-2081 | Unscored | - | 0.4% | - | - |
| CVE-2025-2079 | Unscored | - | 0.4% | - | - |
Common questions
How do I fix CVE-2024-32021?
Published advisories record a fix for 42 affected products. The "How to fix" section on this page lists the fixed version and source advisory for each one, so apply the entry matching what you actually run.
Is CVE-2024-32021 being actively exploited?
Not that we know of. CVE-2024-32021 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 1.0% is the estimated probability that it will be exploited in the next 30 days. That is higher than 60% of all scored CVEs.
How severe is CVE-2024-32021?
CVE-2024-32021 has a CVSS v3 base score of 3.9, rated low. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2024-32021 affect?
Published advisories record a fix for git (Debian), git (Rocky), git (Red Hat / RHEL), git-all (Red Hat / RHEL), and 38 more. Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2024-32021
Markdown
[](https://tridentstack.com/cve/CVE-2024-32021)HTML
<a href="https://tridentstack.com/cve/CVE-2024-32021"><img src="https://tridentstack.com/cve/badge/CVE-2024-32021.svg" alt="CVE-2024-32021"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-01-05.