CVE-2025-24071: Windows File Explorer NTLM Credential Disclosure via Crafted Library Files
- Vendor
- Microsoft Corporation
CVE-2025-24071 is an information disclosure vulnerability classified as spoofing in Microsoft Windows File Explorer. Processing a crafted Windows library description file extracted from an archive can trigger automatic outbound NTLM authentication to an attacker-controlled network resource. An unauthenticated attacker can capture the resulting NTLMv2 challenge-response material without requiring the victim to explicitly open the extracted library file.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation exposes the victim account's NTLM authentication material. Captured challenge-response data can support offline password cracking or, where target services lack effective relay protections, NTLM relay attacks. Subsequent account impersonation, unauthorized access, and lateral movement depend on password strength, account privileges, network reachability, and service protections. The vulnerability does not itself establish arbitrary code execution or privilege escalation.
Mitigation
If you can’t patch tonight, do this now.
Disable NTLM where feasible and migrate authentication to Kerberos. Where NTLM remains necessary, restrict its use and prevent outbound authentication to untrusted network resources. Restrict extraction of untrusted archives and screen archive contents for Windows library description files. Apply appropriate relay protections to destination services to reduce the consequences of coerced authentication; these measures do not replace the Windows security update.
Remediation
Patch, then assume compromise.
Install Microsoft's March 2025 security updates addressing CVE-2025-24071, or superseding cumulative updates, for each affected Windows release. Select the applicable update using Microsoft's product-specific security guidance; exact fixed builds and update identifiers are not available here.
Exploits
27 exploits validated by Mallory's analysis. Hidden: 3 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2025-24071 exploited in the wild?
- Yes. As of Nov 13, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-24071?
- Yes. Mallory tracks 27 public exploits or proofs of concept for CVE-2025-24071, the earliest disclosed Mar 16, 2025.
- Is there a patch for CVE-2025-24071?
- Install Microsoft's March 2025 security updates addressing CVE-2025-24071, or superseding cumulative updates, for each affected Windows release. Select the applicable update using Microsoft's product-specific security guidance; exact fixed builds and update identifiers are not available here.
- What products are affected by CVE-2025-24071?
- Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, and 11 more.
- How severe is CVE-2025-24071?
- CVE-2025-24071 has a CVSS v3.1 score of 6.5 (Medium) and an EPSS score of 23.3% (98th percentile) as of Nov 13, 2026.
Recent activity
26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.