CVE-2024-32465 | Git's protections for cloning untrusted repositories can be bypassed

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.

Published: 2024-05-14 Last update: 2026-01-05 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2024-32465 is rated Moderate Risk (41.8/100): CVSS High severity, with low exploitation likelihood (EPSS 0.15%). Review affected assets and schedule 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-32465

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-02 0.13% 0.15% +0.03%
2 2026-05-13 0.17% 0.13% -0.04%
3 2026-01-06 — 0.17% —

Full EPSS history (10 records total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.3 3.1 HIGH
CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:P)
Hands-on access—USB, keyboard, opening the case—not something you do purely over the wire.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
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.
 0.7 6.0 [email protected]
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
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.
 1.8 5.9 [email protected]

Weakness enumeration for CVE-2024-32465

OS Trackers for CVE-2024-32465

vendor priority summary link
alpine — CVE-2024-32465: 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-32465
debian not yet assigned CVE-2024-32465 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-32465
redhat medium — https://access.redhat.com/security/cve/CVE-2024-32465
suse high CVE-2024-32465 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-32465/
ubuntu medium CVE-2024-32465 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-32465

Affected software / configurations for CVE-2024-32465

Vendor Product Version Raw CPE
git-scm git < 2.39.4 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.40.0, < 2.40.2 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.42.0, < 2.42.2 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git >= 2.43.0, < 2.43.4 cpe:2.3:a:git-scm:git:*:*:*:*:*:*:*:*
git-scm git 2.41.0 cpe:2.3:a:git-scm:git:2.41.0:*:*:*:*:*:*:*
git-scm git 2.44.0 cpe:2.3:a:git-scm:git:2.44.0:*:*:*:*:*:*:*
git-scm git 2.45.0 cpe:2.3:a:git-scm:git:2.45.0:*:*:*:*:*:*:*
fedoraproject fedora 40 cpe:2.3:o:fedoraproject:fedora:40:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
debian debian_linux 11.0 cpe:2.3:o:debian:debian_linux:11.0:*:*:*:*:*:*:*

References for CVE-2024-32465

cvelogic Threat Intelligence