CVE-2024-32465: Git's protections for cloning untrusted repositories can be bypassed
Affects gitSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 7.4 High : upgrade to 2.45.1 soon.
Data as of 13 Nov 2026, 21:02 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.4 |
|---|
- Patch
- Available – fixed in 2.45.1
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 May 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade git to 2.45.1.
Patches and advisories
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewgitpkg:brew/gitOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Git is a revision control system. The Git project recommends to avoid working in untrusted repositories, and instead to clone it first with `git clone --no-local` to obtain a clean copy. Git has specific protections to make that a safe operation even with an untrusted source repository, but vulnerabilities allow those protections to be bypassed. In the context of cloning local repositories owned by other users, this vulnerability has been covered in CVE-2024-32004. But there are circumstances where the fixes for CVE-2024-32004 are not enough: For example, when obtaining a `.zip` file containing a full copy of a Git repository, it should not be trusted by default to be safe, as e.g. hooks could be configured to run within the context of that repository. 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. As a workaround, avoid using Git in repositories that have been obtained via archives from untrusted sources.
References
- openwall.com/lists/oss-security/2024/05/14/2 (opens in a new tab)
- git-scm.com/docs/git (opens in a new tab)
- git-scm.com/docs/git-clone (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/06/msg00018.html (opens in a new tab)
- lists.debian.org/debian-lts-announce/2024/09/msg00009.html (opens in a new tab)
- lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/ (opens in a new tab)
- github.com/CVEProject/cvelistV5/tree/main/cves/2024/32xxx/CVE-2024-32465.json (opens in a new tab)
- github.com/git/git/security/advisories/GHSA-vm9j-46j9-qvq4 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2024-32465 (opens in a new tab)
- github.com/git/git/commit/7b70e9efb18c2cc3f219af399bd384c5801ba1d7 (opens in a new tab)