Skip to main content
Public proof of conceptFix available

CVE-2024-32021

A public proof of concept exists; no exploitation attested.

  • Published2024-05-14
  • Fixed in2.45.1 · 2.44.1 · 2.43.4 · 2.42.2 · 2.41.1 · 2.40.2
  • WeaknessCWE-547

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2024-05-1420:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-32021?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-32021?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

CISA-ADP · NVD · OSV
Git
BranchAffectedFixed in
2.45≥ 2.45.0, < 2.45.12.45.1
2.44≥ 2.44.0, < 2.44.12.44.1
2.43≥ 2.43.0, < 2.43.42.43.4
2.42≥ 2.42.0, < 2.42.22.42.2
2.41≥ 2.41.0, < 2.41.12.41.1
2.40≥ 2.40.0, < 2.40.22.40.2
2.39< 2.39.42.39.4
Git-scm git
BranchAffectedFixed in
2.43≥ 2.43.0, < 2.43.42.43.4
2.42≥ 2.42.0, < 2.42.22.42.2
2.40≥ 2.40.0, < 2.40.22.40.2
2.39< 2.39.42.39.4
2.41= 2.41.0no fix published
2.44= 2.44.0no fix published
2.45= 2.45.0no fix published
Debian debian linux
BranchAffectedFixed in
10.0= 10.0no fix published
11.0= 11.0no fix published

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • gitAlmaLinux:9all versions · fixed in 2.43.5-1.el9_4and 14 other packages
  • gitAlmaLinux:8all versions · fixed in 2.43.5-1.el8_10and 14 other packages

Vendor advisories

  • CVE-2024-32021 Red Hat Product Security153 products fixed · 67 known affected

    git: symlink bypass

    git as a component of Red Hat Enterprise Linux 10 · git-all as a component of Red Hat Enterprise Linux 10 · git-core as a component of Red Hat Enterprise Linux 10 · +64 more

  • RHSA-2024:4368 Red Hat Product Security51 products fixed

    Red Hat Security Advisory: git security update

  • RHSA-2024:4083 Red Hat Product Security51 products fixed

    Red Hat Security Advisory: git security update

  • RHSA-2024:4084 Red Hat Product Security51 products fixed

    Red Hat Security Advisory: git security update

Full record on NVD

Fix

  1. Update Git to 2.45.1 · 2.44.1 · 2.43.4 · 2.42.2 · 2.41.1 · 2.40.2 · 2.39.4
  2. Vendor fix Red Hat Product Security RHSA-2024:4368 · 51 productsFor details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
  3. Workaround from the vendor Red Hat Product Security RHSA-2024:4368 · 51 productsMitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
  4. No fix available, says the vendor Red Hat Product Security CVE-2024-32021 · 35 productsFix deferred
  5. No fix planned, says the vendor Red Hat Product Security CVE-2024-32021 · 32 productsOut of support scope

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionpoc2024-06-11
  • OpenCVESSVC decisionpoc—
  • CNACVSS 3.13.9read 2026-10-23
  • NVDCVSS 3.17.1read 2026-10-23
  • CNAweakness (CWE)CWE-547read 2026-10-23
  • FIRST EPSSEPSS score1.0 %2026-10-22
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Published
2024-05-14
Last Modified
2026-06-17
NVD status
Analyzed

Frequently asked questions

What is CVE-2024-32021?

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.

Is CVE-2024-32021 actively exploited?

A proof-of-concept exploit exists for CVE-2024-32021, but active exploitation has not been confirmed at this time.

What is the CVSS score for CVE-2024-32021?

CVE-2024-32021 has a CVSS v3 base score of 7.1 (HIGH severity), with vector string CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N.

Running git? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database