CVE-2026-32631

Git for Windows: `git clone` from manipulated repositories can leak NTLM hashes to arbitrary servers

Published Apr 15, 2026 CVSS 3.1 · 7.4 High EPSS < 1% KEV · Not listed
Description
Git for Windows is the Windows port of Git. Versions prior to 2.53.0.windows.3 do not have protections that prevent attackers from obtaining a user's NTLM hash. The NTLM hash can be obtained by tricking users into cloning a malicious repository, or checking out a malicious branch, that accesses an attacker-controlled server. By default, NTLM authentication does not need any user interaction. By brute-forcing the NTLMv2 hash (which is expensive, but possible), credentials can be extracted. This issue has been fixed in version 2.53.0.windows.3.

Analysis

AI-generated

Technical impact

Git for Windows versions older than 2.53.0.windows.3 allow an attacker to obtain a user’s NTLM hash by tricking the user into cloning a malicious repository or checking out a malicious branch. The clone operation contacts an attacker-controlled Git server and, via default NTLM authentication, streams the user’s NTLM credentials to the server without requiring any user interaction. The leaked hash can then be brute forced, enabling credential compromise. This vulnerability is an information disclosure flaw (CWE-200).

Affected Systems

Git for Windows, product "Git". Users running any Git for Windows release prior to 2.53.0.windows.3 are affected. Versions 2.53.0.windows.3 and later contain the fix.

Risk and Exploitability

The vulnerability scores a high CVSS of 7.4. EPSS is not reported, indicating that the exploitation probability is not quantified, but the issue is not currently listed in the CISA KEV catalog. The attack vector is inferred to be remote: any actor who can host or trick a user into interacting with a malicious Git server can exploit this flaw. Exploitation requires only that the user run "git clone" or similar commands against the attacker-controlled endpoint. The consequences include potential credential theft and downstream compromise of any resources accessed with those credentials.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Git for Windows to version 2.53.0.windows.3 or later to eliminate the hash leak
  • Disable NTLM authentication in Windows or enforce stronger authentication mechanisms for Git traffic
  • Verify that users do not clone from untrusted or unknown repositories and educate them about the risks of malicious Git servers

Generated by OpenCVE AI on April 15, 2026 at 22:16 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Gitforwindows
Gitforwindows git
Vendors & Products Gitforwindows
Gitforwindows git
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Git for Windows is the Windows port of Git. Versions prior to 2.53.0.windows.3 do not have protections that prevent attackers from obtaining a user's NTLM hash. The NTLM hash can be obtained by tricking users into cloning a malicious repository, or checking out a malicious branch, that accesses an attacker-controlled server. By default, NTLM authentication does not need any user interaction. By brute-forcing the NTLMv2 hash (which is expensive, but possible), credentials can be extracted. This issue has been fixed in version 2.53.0.windows.3.
Title Git for Windows: `git clone` from manipulated repositories can leak NTLM hashes to arbitrary servers
Weaknesses CWE-200
References
Metrics cvssV3_1

{'score': 7.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N'}

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Apr 15, 2026, 6:44 PM
Reserved
Mar 12, 2026, 3:29 PM
Status
Awaiting Analysis
Published
Apr 15, 2026, 6:17 PM
Modified
Jun 17, 2026, 10:36 AM