Quick answers
- Is CVE-2026-20925 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-20925 being exploited in the wild.
- How severe is CVE-2026-20925?
- Medium severity, with a CVSS score of 6.5, published 13 January 2026.
- Which products and versions are affected?
- Microsoft Windows 11 22H3, 23H2, 24H2, 25H2; Microsoft Windows Server 2008 R2 Service Pack 1; Microsoft Windows 10 1607, 1809, 21H2, 22H2.
- Is there a fix for CVE-2026-20925?
- A patch was published on 2026-07-30: Last modified/updated record in MSRC guide Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-20925 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-20925?
- Check whether you run Microsoft Windows 11, Microsoft Windows Server 2008 R2 or Microsoft Windows 10 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability classified as CWE-73 (External Control of File Name or Path) exists in the Windows NTLM implementation. The flaw allows an unauthenticated, remote attacker to influence file paths used during NTLM authentication processes. By inducing a user to interact with a malicious link or resource (User Interaction required), the attacker can trigger NTLM spoofing. This typically results in the disclosure of NTLM hashes or unauthorized credential relaying. Microsoft has released security updates to address this issue across affected Windows and Windows Server versions.
Affected products
- Microsoft Windows 10 1607, 1809, 21H2, 22H2
- Microsoft Windows 11 22H3, 23H2, 24H2, 25H2
- Microsoft Windows Server 2008 R2 Service Pack 1
Timeline
- 2026-01-13: advisory: Initial disclosure by Microsoft and NVD
- 2026-07-30: patched: Last modified/updated record in MSRC guide