CVE-2024-32465

Code execution via partial-clone lazy fetch

Published May 14, 2024 · Updated Nov 4, 2025

Command execution in Git allows attackers to run arbitrary commands after a user invokes Git in an untrusted repository archive. The upload-pack path in a partial repository performs a lazy fetch, allowing repository configuration and hooks to launch attacker-specified commands. Exploitation requires a user to obtain the crafted repository, such as in a ZIP file or on removable media, and then run a clone or fetch operation against it.

CVSS severity7.8
High
EPSS probability1.03%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Command execution in Git allows attackers to run arbitrary commands after a user invokes Git in an untrusted repository archive. The upload-pack path in a partial repository performs a lazy fetch, allowing repository configuration and hooks to launch attacker-specified commands. Exploitation requires a user to obtain the crafted repository, such as in a ZIP file or on removable media, and then run a clone or fetch operation against it.

The record

CVE
CVE-2024-32465
Published
May 14, 2024
Updated
Nov 4, 2025
Vendor
Git
Product
Git
Classifications
CWE-22, T1204.002
Attack vector
physical
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 14, 2024CVE publishedPublication date reported by the CVE source.
  2. Nov 4, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 2.39.4
  2. Affected versionversion=2.39.4* <2.39.4
  3. Affected versionversion=>= 2.40.0, < 2.40.2
  4. Affected versionversion=2.40.0 <=2.40.2
  5. Affected versionversion== 2.41.0
  6. Affected versionversion=2.41.0
  7. Affected versionversion=>= 2.42.0, < 2.42.2
  8. Affected versionversion=2.42.0 <=2.42.2
  9. Affected versionversion=>= 2.43.0, < 2.43.4
  10. Affected versionversion=2.43.0 <=2.43.4
  11. Affected versionversion== 2.44.0
  12. Affected versionversion=2.44.0
  13. Affected versionversion== 2.45.0
  14. Affected versionversion=2.45.0

What conditions does exploitation require?

Attack vectorphysical
Required privilegesunauthenticated

What is affected?

Git · Gitversion=< 2.39.4; version=2.39.4* <2.39.4; version=>= 2.40.0, < 2.40.2; version=2.40.0 <=2.40.2; version== 2.41.0; version=2.41.0; version=>= 2.42.0, < 2.42.2; version=2.42.0 <=2.42.2; version=>= 2.43.0, < 2.43.4; version=2.43.0 <=2.43.4; version== 2.44.0; version=2.44.0; version== 2.45.0; version=2.45.0

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
7.3GitHub, Inc.CVSS:3.1/AV:P/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorphysical
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
T1204.002User Execution: Malicious File

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo