Is this vulnerability remotely exploitable?

Yes. An attacker can exploit it remotely by operating a malicious Git server or endpoint and convincing a victim to perform a clone operation against it, which can cause the client to send NTLM hashes.

What level of access does an attacker need to exploit this issue?

The attacker needs control over a Git server or network endpoint and the ability to persuade the victim to connect to it (for example, by sending a crafted repository URL). No prior access to the victim's machine is required beyond their normal Git usage.

What is the safest general fix pattern for developers and administrators?

Use authentication schemes that do not expose reusable password hashes (such as SSH keys or access tokens), restrict NTLM or integrated authentication to trusted domains and hosts, and configure Git clients so that system credentials are not automatically sent to arbitrary servers.

Severity:

HIGH RISK

(7.4)

Information Exposure via NTLM Hash Leakage (CWE-200) in Git for Windows Clone Operation

CVE-2025-66413

Published:

Mar 10, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Information Exposure

CWE:

CWE-200;CWE-307

Impact:

Credential Exposure and Account Compromise

Severity:

HIGH RISK

(7.4)

CVSS Version:

3.1

Vulnerability Type

Category:

Information Exposure

CWE:

CWE-200;CWE-307

Impact:

Credential Exposure and Account Compromise

Severity:

HIGH RISK

(7.4)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Information Exposure via NTLM Hash Leakage (CWE-200) in Git for Windows Clone Operation

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal