Loading vulnerability…
Git for Windows versions prior to 2.53.0.windows.3 lack protections to prevent disclosure of a user's NTLM hash during repository operations. An attacker can craft a malicious repository or branch such that, when a victim clones the repository or checks out the branch, Git for Windows accesses an attacker-controlled server and automatically attempts NTLM authentication. Because NTLM authentication can occur by default without additional user interaction, the attacker can capture the victim's NTLMv2 challenge-response material. The issue is described as enabling attackers to obtain a user's NTLM hash and was fixed in Git for Windows 2.53.0.windows.3.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.