# CVE-2026-32631: Git for Windows: `git clone` from manipulated repositories can leak NTLM hashes to arbitrary servers

> Attackers can leak NTLM hashes by tricking users into cloning malicious repositories, potentially leading to credential extraction.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Apr 2026
- **Updated:** 15 Apr 2026
- **Also known as:** GHSA-9j5h-h4m7-85hx, MINI-2wq2-46gw-76pf

## What is CVE-2026-32631?

CVE-2026-32631 is a high-severity vulnerability in git-for-windows git, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-32631?


## How do I fix CVE-2026-32631?

Upgrade to a fixed version.

## Is CVE-2026-32631 being exploited?

There is no known exploitation of CVE-2026-32631 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32631 and fix it if it is affected.

What it is: CVE-2026-32631 is a high-severity vulnerability in git-for-windows git, published on 15 Apr 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-32631 in the wild and no public exploit code.

Affected product: git-for-windows git. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32631/ (Markdown: https://insights.sbomify.com/CVE-2026-32631/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32631
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32631
- OSV: https://osv.dev/vulnerability/CVE-2026-32631

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32631/
Summaries are generated and may contain mistakes; the official description above is the record.