Git for Windows NTLM Hash Leak Poses Credential Risk
A notable vulnerability, tracked as CVE-2026-32631, has been identified in Git for Windows. According to the National Vulnerability Database, versions prior to 2.53.0.windows.3 lack critical protections against NTLM hash exposure. This isn’t just a theoretical flaw; an attacker can exploit this by enticing users to clone a malicious repository or check out a compromised branch. The kicker? NTLM authentication typically requires no user interaction, making this a stealthy attack vector.
The National Vulnerability Database highlights that once an NTLM hash is obtained, it opens the door to offline brute-forcing. While NTLMv2 hashes are computationally expensive to crack, it’s far from impossible for a determined adversary. Successful cracking means credentials are laid bare, potentially leading to broader network compromise. This vulnerability, rated 7.4 (High Severity) on the CVSS scale, underscores the persistent risk associated with NTLM and the need for robust controls around development tools.
Related ATT&CK Techniques
🛡️ Detection Rules
3 rules · 6 SIEM formats3 auto-generated detection rules for this incident, mapped to MITRE ATT&CK. Available in Sigma, Splunk SPL, Sentinel KQL, Elastic Lucene, QRadar AQL, and Wazuh.
Credential Abuse from Breached Vendor — CVE-2026-32631
Want this in your SIEM's native format? Get Splunk SPL, Sentinel KQL, Elastic, QRadar AQL, or Wazuh — ready to paste.
3 Sigma rules mapped to the ATT&CK techniques from this breach — pick your SIEM and get a ready-to-paste query.
Get All SIEM Formats →Indicators of Compromise
| ID | Type | Indicator |
|---|---|---|
| CVE-2026-32631 | Information Disclosure | Git for Windows versions prior to 2.53.0.windows.3 |
| CVE-2026-32631 | Information Disclosure | NTLM hash disclosure via malicious Git repository clone or branch checkout |