CVE-2025-66413
NTLM Hash Exposure in Git for Windows via Malicious Clone
Publication date: 2026-03-10
Last updated on: 2026-04-21
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gitforwindows | git | to 2.53.0 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
| CWE-307 | The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Git for Windows versions prior to 2.53.0(2). An attacker can trick a user into cloning a repository from a malicious server, which allows the attacker to obtain the user's NTLM hash.
Because NTLM hashing is weak, the attacker can then brute-force the user's account name and password using the obtained hash.
This issue is fixed in Git for Windows version 2.53.0(2).
How can this vulnerability impact me? :
If exploited, this vulnerability can lead to an attacker obtaining your NTLM hash and subsequently brute-forcing your account credentials.
This can result in unauthorized access to your user account, potentially compromising your system or data.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, you should upgrade Git for Windows to version 2.53.0(2) or later, where the issue has been fixed.