CVE-2024-32002

CVE-2024-32002 is a critical-severity vulnerability in Git with a CVSS 3.x base score of 9.0. Its EPSS exploit-prediction score of 25% places it in the 98th percentile, indicating an elevated likelihood of exploitation. The underlying weakness is classified as CWE-59.

Key facts

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, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. 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. If symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks false`), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.

Frequently asked questions

What is CVE-2024-32002?
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, repositories with submodules can be crafted in a way that exploits a bug in Git whereby it can be fooled into writing files not into the submodule's worktree but into a `.git/` directory. This allows writing a hook that will be executed while the clone operation is still running, giving the user no opportunity to inspect the code that is being executed. 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. If symbolic link support is disabled in Git (e.g. via `git config --global core.symlinks false`), the described attack won't work. As always, it is best to avoid cloning repositories from untrusted sources.
How severe is CVE-2024-32002?
CVE-2024-32002 has a CVSS 3.x base score of 9.0, rated critical severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2024-32002 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 25% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2024-32002?
CVE-2024-32002 primarily affects Git. In total, 4 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2024-32002?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2024-32002 have an EU (EUVD) identifier?
Yes. CVE-2024-32002 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2024-29843.
When was CVE-2024-32002 published?
CVE-2024-32002 was published on 2024-05-14 and last updated on 2026-06-17.

References

Affected products (4)

More vulnerabilities in Git

All CVEs affecting Git →

Other CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities

Browse all CWE-59 (Improper Link Resolution Before File Access (Link Following)) vulnerabilities →