CVE-2024-32002 | Git's recursive clones on case-insensitive filesystems that support symlinks are susceptible to Remote Code Execution

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.

Published: 2024-05-14 Last update: 2025-11-04 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-32002 is rated High Risk (65.1/100): CVSS Critical severity, with high exploitation likelihood (EPSS 22.53%, 97th percentile). EPSS ranks this CVE among the most likely to be exploited in the near term. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2024-32002

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 80.58% 22.53% -58.05%
2 2026-06-12 80.84% 80.58% -0.26%
3 2026-06-11 — 80.84% —

Full EPSS history (60 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2024-32002

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 6.0 [email protected]
9.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.2 6.0 [email protected]

Weakness enumeration for CVE-2024-32002

OS Trackers for CVE-2024-32002

vendor priority summary link
alpine — CVE-2024-32002: 1 source package rows (git); 75 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 68. https://security.alpinelinux.org/vuln/CVE-2024-32002
debian not yet assigned CVE-2024-32002 not yet assigned priority: Debian including 1 source packages (git), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2024-32002
redhat high — https://access.redhat.com/security/cve/CVE-2024-32002
suse high CVE-2024-32002 severity important: SUSE including 150 source package names (0.0.17-1.1:git-core-2.43.0-150600.3.3.1, 0.1.6-1.2:git-2.43.0-150600.3.3.1, …), 418 product×package rows across 63 product lines (Container bci/gcc, Container bci/golang, … (63 product lines)): Fixed 344, Known Not Affected 74. https://www.suse.com/security/cve/CVE-2024-32002/
ubuntu medium CVE-2024-32002 medium priority: Ubuntu including 1 source packages (git), 7 status rows across 7 suites (bionic, focal, jammy, mantic, noble, upstream, xenial): released 6, not-affected 1. https://ubuntu.com/security/CVE-2024-32002

Affected software / configurations for CVE-2024-32002

Vendor Product Version Raw CPE
git git < 2.39.4 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.40.0, < 2.40.2 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.42.0, < 2.42.2 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git >= 2.43.0, < 2.43.4 cpe:2.3:a:git:git:*:*:*:*:*:*:*:*
git git 2.41.0 cpe:2.3:a:git:git:2.41.0:*:*:*:*:*:*:*
git git 2.44.0 cpe:2.3:a:git:git:2.44.0:*:*:*:*:*:*:*
git git 2.45.0 cpe:2.3:a:git:git:2.45.0:*:*:*:*:*:*:*

References for CVE-2024-32002

cvelogic Threat Intelligence