CVE-2026-32631: GitHub: CVE-2026-32631 'git clone' from manipulated repositories can leak NTLM hashes
CVE-2026-32631 is an information disclosure vulnerability in GitHub, rated Important by Microsoft, with a CVSS 3.1 base score of 7.4 (High). An attacker can exploit it remotely over the network, without any privileges and only if a user takes an action. Microsoft has not reported exploitation in the wild and rates exploitation as less likely. The EPSS model estimates a 0.32% probability of exploitation activity in the next 30 days, higher than 25% of all scored vulnerabilities. Microsoft released the fix on 14 April 2026 in the April 2026 Patch Tuesday. It affects 5 products in 1 product family (Developer Tools).
Key facts
- CVE ID
- CVE-2026-32631
- Severity
- High CVSS 7.4
- Microsoft severity
- Important
- Impact
- Information Disclosure
- Exploited in the wild
- No
- Publicly disclosed
- No
- Exploitation likelihood
- Less Likely
- Weakness
- CWE-200
- EPSS
- 0.32% (percentile 25%)
- CISA KEV
- Not listed
- Released
- Last updated
- Patch Tuesday
- April 2026 Patch Tuesday
- Product families
- Developer Tools
CVSS score and vector
Microsoft scores CVE-2026-32631 at 7.4 (temporal 6.4) using CVSS 3.1. Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N/E:U/RL:O/RC:C
| Metric | Value |
|---|---|
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | None |
| User interaction | Required |
| Scope | Changed |
| Confidentiality impact | High |
| Integrity impact | None |
| Availability impact | None |
| Exploit code maturity | Unproven |
| Remediation level | Official fix |
| Report confidence | Confirmed |
Description
CVE-2026-32631 is regarding a vulnerability where it is possible to obtain a user's NTLM hash by tricking them 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. GitHub created this CVE on their behalf. The documented Visual Studio updates incorporate updates in Git which address this vulnerability.
Please see CVE-2026-32631 for more information.
Affected products (5)
Developer Tools
| Product | Security update | Type | Fixed build | Restart |
|---|---|---|---|---|
| Microsoft Visual Studio 2019 version 16.4 (includes 16.0 - 16.3) | Release Notes | Security Update | 16.11.55 | Maybe |
| Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) | Release Notes | Security Update | 15.9.79 | Maybe |
| Microsoft Visual Studio 2022 version 17.12 | Release Notes | Security Update | 17.12.19 | Maybe |
| Microsoft Visual Studio 2022 version 17.14 | Release Notes | Security Update | 17.14.30 | Maybe |
| Microsoft Visual Studio 2026 version 18.4 | Release Notes | Security Update | 18.4.4 | Maybe |
NIST NVD data
- NVD status
- Awaiting Analysis
- NVD CVSS
- 7.4 (HIGH)
- NVD weakness
- CWE-200
- Published to NVD
- NVD last modified
References
- https://github.com/git-for-windows/git/releases/tag/v2.53.0.windows.3
- https://github.com/git-for-windows/git/security/advisories/GHSA-9j5h-h4m7-85hx
- https://learn.microsoft.com/en-au/windows/whats-new/deprecated-features#:~:text=NTLM
- https://support.microsoft.com/en-us/topic/upcoming-changes-to-ntlmv1-in-windows-11-version-24h2-and-windows-server-2025-c0554217-cdbc-420f-b47c-e02b2db49b2e
- https://techcommunity.microsoft.com/blog/windows-itpro-blog/the-evolution-of-windows-authentication/3926848
Revision history
| Version | Date | Description |
|---|---|---|
| 1.0 | Information published. |