CVE-2025-66413: Git for Windows is the Windows port of Git

Q: How do I fix CVE-2025-66413?

git: upgrade to newer than 2.53.0. Exact commands for each OS are on this page.

Q: Is CVE-2025-66413 being exploited?

CVE-2025-66413 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-66413 affect?

CVE-2025-66413 affects git. Severity is high (CVSS 7.4). Git for Windows is the Windows port of Git. Prior to 2.53.0(2), it is possible to obtain a user's NTLM hash by tricking them into cloning from a malicious server. Since NTLM hashing is weak, it is possible for the attacker to brute-force th

Q: How urgent is CVE-2025-66413?

Priority 36/100. High severity; Public exploit reference

Routine

HIGH 7.4UPGRADE

CVE-2025-66413 is a high-severity flaw (CVSS 7.4) affecting git. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Git for Windows is the Windows port of Git. Prior to 2.53.0(2), it is possible to obtain a user's NTLM hash by tricking them into cloning from a malicious server. Since NTLM hashing is weak, it is possible for the attacker to brute-force the user's account name and password. This vulnerability is fixed in 2.53.0(2).

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.4 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-200, CWE-307
Published	2026-03-10
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: gitforwindows

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-10 21:16 UTCPublished CVE record published
2026-06-17 09:56 UTCUpdated Record last modified

gitforwindows git UPGRADE

Affected: <= 2.53.0

Fixed in: newer than 2.53.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy git || rpm -q git || git --version

2. UPGRADE to newer than 2.53.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade git

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade git

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-66413?

git: upgrade to newer than 2.53.0. Exact commands for each OS are on this page.

Is CVE-2025-66413 being exploited?

CVE-2025-66413 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-66413 affect?

CVE-2025-66413 affects git. Severity is high (CVSS 7.4). Git for Windows is the Windows port of Git. Prior to 2.53.0(2), it is possible to obtain a user's NTLM hash by tricking them into cloning from a malicious server. Since NTLM hashing is weak, it is possible for the attacker to brute-force th

How urgent is CVE-2025-66413?

Priority 36/100. High severity; Public exploit reference

Software pages

Windows vulnerabilities · Git vulnerabilities

Related CVEs

CVE-2025-48384 HIGH 8.0 EXPLOITED UPGRADE MITIGATE Git Link Following Vulnerability
CVE-2024-52006 HIGH 7.5 UPGRADE MITIGATE Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides
CVE-2024-52005 HIGH 8.8 UPGRADE Git is a source code management tool
CVE-2024-50349 MEDIUM 4.7 MITIGATE UPGRADE Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides

References

← Back to latest CVEs