CVE-2024-32004 [High]

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, an attacker can prepare a local repository in such a way that, when cloned, will execute arbitrary code during the operation. 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 cloning repositories from untrusted sources.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-02	2.77%	2.44%	-0.33%
2	2026-05-13	2.43%	2.77%	+0.35%
3	2026-04-09	—	2.43%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-02

2.77%

2.44%

-0.33%

2026-05-13

2.43%

2.77%

+0.35%

2026-04-09

—

2.43%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
8.1	3.1	HIGH	`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/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: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.	1.4	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]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

8.1

3.1

HIGH

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/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: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.

1.4

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]

OS Trackers for CVE-2024-32004

vendor	priority	summary	link
`alpine`	—	CVE-2024-32004: 1 source package rows (git); 73 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 66.	https://security.alpinelinux.org/vuln/CVE-2024-32004
`debian`	not yet assigned	CVE-2024-32004 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-32004
`redhat`	high	—	https://access.redhat.com/security/cve/CVE-2024-32004
`suse`	high	CVE-2024-32004 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-32004/
`ubuntu`	medium	CVE-2024-32004 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-32004

Affected software / configurations for CVE-2024-32004

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-32004

URL	Tags
http://www.openwall.com/lists/oss-security/2024/05/14/2	Mailing List Third Party Advisory
https://git-scm.com/docs/git-clone	Technical Description
https://github.com/git/git/commit/f4aa8c8bb11dae6e769cd930565173808cbb69c8	Patch
https://github.com/git/git/security/advisories/GHSA-xfc6-vwr8-r389	Vendor Advisory
https://lists.debian.org/debian-lts-announce/2024/06/msg00018.html	Mailing List Vendor Advisory
https://lists.fedoraproject.org/archives/list/[email protected]/message/S4CK4IYTXEOBZTEM5K3T6LWOIZ3S44AR/	Mailing List Vendor Advisory
https://lists.debian.org/debian-lts-announce/2024/09/msg00009.html	Mailing List Vendor Advisory

URL

CVE-2024-32004 | Git vulnerable to Remote Code Execution while cloning special-crafted local repositories

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

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

Weakness enumeration for CVE-2024-32004

OS Trackers for CVE-2024-32004

Affected software / configurations for CVE-2024-32004

References for CVE-2024-32004