CVE-2024-32465

Git's protections for cloning untrusted repositories can be bypassed

HIGH

7.8

CVSS Score

Published: May 14, 2024 at 07:18 PM UTC

Updated: June 17, 2026 at 07:29 AM UTC

4 products affected across 4 vendorsDebian LinuxFedoraGit

Using git by git?

Get instant alerts when new vulnerabilities affect git - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

HIGH7.8

Exploit prediction

EPSS 1%

SSVC

No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Debian Linux · Debiandrupal

95%

10.0 11.0

Fedora · Fedora Projectrpm

95%

Git · Git Scm

95%

v < 2.39.42.40.0 ≤ v < 2.40.22.42.0 ≤ v < 2.42.22.43.0 ≤ v < 2.43.42.41.0 2.44.0 2.45.0

Git · Gitrubygems

60%

v < 2.39.4v < 2.40.2v < 2.42.2v < 2.43.42.39.4* ≤ v < 2.39.42.40.0 ≤ v ≤ 2.40.22.42.0 ≤ v ≤ 2.42.22.43.0 ≤ v ≤ 2.43.42.39.4*2.40.0 2.41.0 2.42.0 2.43.0 2.44.0 2.45.0= 2.41.0= 2.44.0= 2.45.0

Affected range stops below 2.39.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.40.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.42.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.43.4, so it looks safe — our inference, not a vendor statement