CVE-2026-32631 json
Git for Windows: `git clone` from manipulated repositories can leak NTLM hashes to arbitrary servers
published 2026-04-15 6 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-22991
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- git_for_windows_project git_for_windows 2.53.0.3
- gitforwindows git 2.53.0.3
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.32% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N |
Affected products
- git-for-windows git
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
- github.com /git-for-windows/git/security/advisories/GHSA-9j5h-h4m7-85hx
- github.com /git-for-windows/git/releases/tag/v2.53.0.windows.3
- learn.microsoft.com /en-au/windows/whats-new/deprecated-features#:~:text=NTLM
- support.microsoft.com /en-us/topic/upcoming-changes-to-ntlmv1-in-windows-11-version-24h2-and-windows-server-2025-c0554217-cdbc-420f-
- techcommunity.microsoft.com /blog/windows-itpro-blog/the-evolution-of-windows-authentication/3926848
Sources
- CVE List CVE-2026-32631
- NVD CVE-2026-32631
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.