Microsoft Windows 10
NTLM Hash Disclosure Spoofing Vulnerability
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 10.0.10240.0, < 10.0.10240.20947
Fixed in 10.0.10240.20947
- >= 10.0.14393.0, < 10.0.14393.7876
Fixed in 10.0.14393.7876
- >= 10.0.17763.0, < 10.0.17763.7009
Fixed in 10.0.17763.7009
- >= 10.0.19044.0, < 10.0.19044.5608
Fixed in 10.0.19044.5608
- >= 10.0.19045.0, < 10.0.19045.5608
Fixed in 10.0.19045.5608
- >= 10.0.22621.0, < 10.0.22621.5039
Fixed in 10.0.22621.5039
- >= 10.0.22631.0, < 10.0.22631.5039
Fixed in 10.0.22631.5039
- >= 10.0.22631.0, < 10.0.22631.5039
Fixed in 10.0.22631.5039
- >= 10.0.26100.0, < 10.0.26100.3476
Fixed in 10.0.26100.3476
- >= 6.1.7601.0, < 6.1.7601.27618
Fixed in 6.1.7601.27618
- >= 6.1.7601.0, < 6.1.7601.27618
Fixed in 6.1.7601.27618
- >= 6.2.9200.0, < 6.2.9200.25368
Fixed in 6.2.9200.25368
- >= 6.2.9200.0, < 6.2.9200.25368
Fixed in 6.2.9200.25368
- >= 6.3.9600.0, < 6.3.9600.22470
Fixed in 6.3.9600.22470
- >= 6.3.9600.0, < 6.3.9600.22470
Fixed in 6.3.9600.22470
- >= 10.0.14393.0, < 10.0.14393.7876
Fixed in 10.0.14393.7876
- >= 10.0.14393.0, < 10.0.14393.7876
Fixed in 10.0.14393.7876
- >= 10.0.17763.0, < 10.0.17763.7009
Fixed in 10.0.17763.7009
- >= 10.0.17763.0, < 10.0.17763.7009
Fixed in 10.0.17763.7009
- >= 10.0.20348.0, < 10.0.20348.3328
Fixed in 10.0.20348.3328
- >= 10.0.25398.0, < 10.0.25398.1486
Fixed in 10.0.25398.1486
- >= 10.0.26100.0, < 10.0.26100.3476
Fixed in 10.0.26100.3476
- >= 10.0.26100.0, < 10.0.26100.3476
Fixed in 10.0.26100.3476
Mitigation
Upgrade Windows 10 Version 1507 to 10.0.10240.20947 or later.
Upgrade Windows 10 Version 1607 to 10.0.14393.7876 or later.
Upgrade Windows 10 Version 1809 to 10.0.17763.7009 or later.
Upgrade Windows 10 Version 21H2 to 10.0.19044.5608 or later.
Upgrade Windows 10 Version 22H2 to 10.0.19045.5608 or later.
Upgrade Windows 11 version 22H2 to 10.0.22621.5039 or later.
Upgrade Windows 11 version 22H3 to 10.0.22631.5039 or later.
Upgrade Windows 11 Version 23H2 to 10.0.22631.5039 or later.
Upgrade Windows 11 Version 24H2 to 10.0.26100.3476 or later.
Upgrade Windows Server 2008 R2 Service Pack 1 to 6.1.7601.27618 or later.
Upgrade Windows Server 2008 R2 Service Pack 1 (Server Core installation) to 6.1.7601.27618 or later.
Upgrade Windows Server 2012 to 6.2.9200.25368 or later.
Upgrade Windows Server 2012 (Server Core installation) to 6.2.9200.25368 or later.
Upgrade Windows Server 2012 R2 to 6.3.9600.22470 or later.
Upgrade Windows Server 2012 R2 (Server Core installation) to 6.3.9600.22470 or later.
Upgrade Windows Server 2016 to 10.0.14393.7876 or later.
Upgrade Windows Server 2016 (Server Core installation) to 10.0.14393.7876 or later.
Upgrade Windows Server 2019 to 10.0.17763.7009 or later.
Upgrade Windows Server 2019 (Server Core installation) to 10.0.17763.7009 or later.
Upgrade Windows Server 2022 to 10.0.20348.3328 or later.
Upgrade Windows Server 2022, 23H2 Edition (Server Core installation) to 10.0.25398.1486 or later.
Upgrade Windows Server 2025 to 10.0.26100.3476 or later.
Upgrade Windows Server 2025 (Server Core installation) to 10.0.26100.3476 or later.
References
- Vendor advisory msrc.microsoft.com/update-guide/vulnerability/CVE-2025…
Timeline
Days relative to CVE publicationFirst public PoC 38 days after publication; added to CISA KEV 37 days after publication. First PoC: basekilll/CVE-2025-24054_PoC (created 18 Apr 2025, found by us: backfilled).
PoC repositories
Found on GitHub.7 PoCs · 2 informational · 4 not a PoC · 6 suspicious or fake
PoCs 7
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| basekilll/CVE-2025-24054_PoC | 18 Apr 2025 +38 d | 4 | PoC |
| xigney/CVE-2025-24054_PoC | 18 Apr 2025 +38 d | 4 | PoC |
| helidem/CVE-2025-24054_CVE-2025-24071-PoC | 22 Apr 2025 +42 d | 22 | PoC |
| S4mma3l/CVE-2025-24054 | 1 May 2025 +51 d | 0 | PoC via PoC Index |
| moften/CVE-2025-24054 | 19 May 2025 +69 d | 1 | PoC via PoC Index |
| nexus956/CVE-2025-24054-PoC | 1 May 2026 +1.1 y | 0 | PoC |
| simantchaudhari/CVE-2025-24054-PoC | 1 May 2026 +1.1 y | 0 | PoC |
Informational 2
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Wind010/CVE-2025-24054_PoC | 9 Nov 2025 +243 d | 0 | Informational · write-up |
| T0tooro/cve-2025-24054-lab | 1 Jul 2026 +1.3 y | 0 | Informational · detection
Flags · score 35
Below the suspicion threshold (50); does not change the assessment. |
Not a PoC 4
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| 0x6rss/CVE-2025-24071_PoC | 16 Mar 2025 +5.1 d | 414 | Not a PoC · unrelated |
| pswalia2u/CVE-2025-24071_POC | 21 Apr 2025 +41 d | 0 | Not a PoC · unrelated |
| Royall-Researchers/CVE-2025-24071 | 5 Jul 2025 +116 d | 0 | Not a PoC · unrelated |
| Fomovet/cve-2025-24071 | 21 Jun 2026 +1.3 y | 0 | Not a PoC · unrelated |
Suspicious or fake 6
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| Marcejr117/CVE-2025-24071_PoC | 27 Mar 2025 +16 d | 24 | Fake |
| rubenformation/CVE-2025-50154 | 13 Aug 2025 +155 d | 55 | Suspicious · score 50
Why suspicious
|
| Untouchable17/CVE-2025-24054 | 23 Nov 2025 +257 d | 2 | Fake |
| SecurityLayer404/CVE-2025-24054-24071---Metasploit-Module | 1 Apr 2026 +1.1 y | 0 | Fake |
| kaleth4/CVE--2025-24054 | 3 Apr 2026 +1.1 y | 0 | Fake |
| Fomovet/cve-2025-24054 | 21 Jun 2026 +1.3 y | 0 | Fake |
Only PoCs count toward the first-PoC date and the characteristics below. Suspicious repositories (score ≥ 50) never count. Do not run PoC code from unknown sources.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| Exploit-DB | Microsoft - NTLM Hash Disclosure Spoofing (library-ms) | 1 May 2025 | 14 Nov 2026 |
| Exploit-DB | windows 10/11 - NTLM Hash Disclosure Spoofing | 4 Feb 2026 | 14 Nov 2026 |
| Exploit-DB | Windows 10.0.17763.7009 - spoofing vulnerability | 11 Feb 2026 | 14 Nov 2026 |