CVE-2024-32021

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account, but needs a user to act. Limited direct impact.

Exploit odds

1.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2024-05-14 20:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 07:29 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.0% in the next 30 days (EPSS).
• Severity: 3.9 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2024-05-14 20:15 UTC

Last modified

2026-06-17 07:29 UTC

Exploit probability

1.0% · EPSS, next 30 days

Weakness

CWE-547

Record status

Analyzed

Affected

• git-scm Git < 2.39.4
• git-scm Git < 2.40.2
• git-scm Git < 2.42.2
• git-scm Git < 2.43.4
• git-scm Git 2.41.0
• git-scm Git 2.44.0
• git-scm Git 2.45.0
• Fedoraproject Fedora 40

Attack profile CVSS 3.1 · 3.9

Attack vector

Local

Complexity

High

Privileges needed

Low

User interaction

Required

Scope

Changed

Confidentiality

None

Integrity

Low

Availability

Low

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2024-32021.md and follow it. Check whether this project is affected by CVE-2024-32021. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge