dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-32631

HIGH · 7.4 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Git for Windows versions prior to 2.53.0.windows.3 lack protections against NTLM hash extraction. Attackers can obtain a user's NTLM hash by tricking users into cloning a malicious repository or checking out a malicious branch that connects to an attacker-controlled server. Since NTLM authentication does not require user interaction by default, the NTLMv2 hash can be captured and potentially brute-forced to extract credentials.

MitigationUpgrade Git for Windows to version 2.53.0.windows.3 or later to obtain the NTLM hash protection fixes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Git for Windows is installed
    Open Command Prompt or PowerShell and run: git --version
    Affected if If the command returns a version number, Git for Windows is installed. If 'git' is not recognized, Git for Windows is not present.
  2. Identify the installed Git for Windows version
    Run: git --version. The output will show a version string like 'git version 2.x.x.windows.x'
    Affected if The full version string is displayed. Capture this for comparison against the affected range.
  3. Compare your version against the affected range
    Compare the version number from step 2 against 2.53.0.windows.3. Versions prior to 2.53.0.windows.3 are affected (for example: 2.52.0.windows.1, 2.51.0.windows.1, etc.)
    Affected if If your version is lower than 2.53.0.windows.3 (for example: 2.52.0.windows.1), your installation is vulnerable.
  4. Verify NTLM credential helper configuration (optional context)
    Run: git config --global --list and look for entries containing 'credential' or 'NTLM'
    Affected if If a credential helper is configured that uses NTLM authentication, the environment is susceptible to hash extraction if a user clones from an attacker-controlled server.

If Git for Windows is installed and the version is lower than 2.53.0.windows.3, the environment is vulnerable to NTLM hash extraction attacks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Git for Windows to version 2.53.0.windows.3 or later to obtain the NTLM hash protection fixes.

Recommended fix High confidence

2.53.0.windows.3

  1. Verify current Git for Windows version by running `git --version` in Command Prompt or PowerShell
  2. Download Git for Windows version 2.53.0.windows.3 or later from the official Git website (git-scm.com) or GitHub releases
  3. Run the installer and follow the installation wizard prompts
  4. Alternatively, update via winget: `winget install Git.Git --version 2.53.0` or via Chocolatey: `choco upgrade git -y`
  5. After installation, verify the upgrade by running `git --version` to confirm version 2.53.0.windows.3 or later is installed

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32631 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32631 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data