CVSS base score: 7.4 (High) vendor CNA · v3.1
Score assigned by the vendor's own CVE Numbering Authority (CNA); CISA's Vulnrichment program adds a score only when the CNA omits one.
Vendor: git Product: git
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.
Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 135 points from 2024-05-18, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 1.0% on 2026-08-08.
Check whether a specific version is affected →
What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.
No mentions found in monitored research blogs or news feeds.
Coverage across public collections only: Nuclei and OpenVAS NVT (scan);
Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM);
Metasploit, Exploit-DB and public GitHub repositories (exploit). Absence
here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by
PoC-in-GitHub (CC0) and are not vetted:
some are fakes and some are malware. Treat them as evidence that code was
published, not as code to run.
OpenVAS coverage derives from the Greenbone Community Feed, made available
under the Open Database License (ODbL) v1.0;
its individual Vulnerability Tests are licensed
GNU GPL v2.
Where the distribution has shipped a fix, and in which version. Green means the release has resolved it, amber that it is still open. Data from the Debian Security Tracker, used under Debian's MIT / GPLv2+ terms. Debian is upstream of several other distributions, so a fix here often precedes theirs.
Defensive techniques inferred by MITRE D3FEND from the underlying weakness (CWE-22) — general hardening and detection guidance for this weakness class, not a vendor patch for this specific CVE.
| Source | Date | Record |
|---|---|---|
| CISA Vulnrichment | 2024-05-15 | source record → |
| Date | Advisory | Issuer |
|---|---|---|
| 2024-05-22 | 2024-046: Multiple Vulnerabilities in Git | CERT-EU |
No exploit-tool sightings recorded for this CVE.
Evidence tiers are explained on the About page — a merged Metasploit module is far stronger evidence than a distro package mention.
CVE.org record → NVD entry → FortiGuard Labs → Rapid7 AttackerKB →