Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 15 Apr 2026 21:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitforwindows
Gitforwindows git |
|
| Vendors & Products |
Gitforwindows
Gitforwindows git |
Wed, 15 Apr 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 15 Apr 2026 17:45:00 +0000
| 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
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-15T18:44:04.155Z
Reserved: 2026-03-12T15:29:36.559Z
Link: CVE-2026-32631
Updated: 2026-04-15T18:43:58.924Z
Status : Awaiting Analysis
Published: 2026-04-15T18:17:17.437
Modified: 2026-04-17T15:38:09.243
Link: CVE-2026-32631
No data.
OpenCVE Enrichment
Updated: 2026-04-15T22:30:16Z