CVE-2025-24054: Microsoft Windows NTLM Hash Disclosure Spoofing Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.
Description quoted from the CVE record (assigned by microsoft, published 2025-03-11).
Weakness: CWE-73: External Control of File Name or Path
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality high, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: partial.
- On CISA KEV since
- 2025-04-17
- US federal deadline
- 2025-05-08
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2025-02760, CNNVD-202503-1251, EDB-52280, EDB-52478, EDB-52480, EUVD-2025-6336, GHSA-6v67-599p-fprc
VEDAS cluster: VEDAS:ASHENBOUGH
Exploit Observer links 24 pieces of public exploit code or detection modules that name this CVE or one of its aliases.
Exploit code and modules (24)
Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.
- Exploit-DB: https://www.exploit-db.com/raw/52280
- Exploit-DB: https://www.exploit-db.com/raw/52280
- Exploit-DB: https://www.exploit-db.com/raw/52478
- Exploit-DB: https://www.exploit-db.com/raw/52478
- Exploit-DB: https://www.exploit-db.com/raw/52480
- Exploit-DB: https://www.exploit-db.com/raw/52480
- Code repository: https://github.com/basekilll/cve-2025-24054_poc
- Code repository: https://github.com/clementnjeru/cve-2025-24054-poc
- Code repository: https://github.com/dukesec97/cve-2025-24054
- Code repository: https://github.com/fomovet/cve-2025-24054
- Code repository: https://github.com/helidem/cve-2025-24054-poc
- Code repository: https://github.com/helidem/cve-2025-24054_cve-2025-24071-poc
- and 12 more
Research and write-ups (7)
- Research or write-up: https://avleonov.com/2025/05/08/1532-about-spoofing-windows-ntlm-cve-2025-24054-vulne
- Research or write-up: https://old.rapid7.com/db/vulnerabilities/microsoft-windows-cve-2025-24054
- Research or write-up: https://ptsecurity.com/research/trending-vulnerabilities/CVE-2025-24054
- Research or write-up: https://ptsecurity.com/ru-ru/research/trending-vulnerabilities/CVE-2025-24054
- Research or write-up: https://research.checkpoint.com/2025/cve-2025-24054-ntlm-exploit-in-the-wild
- Research or write-up: https://www.ptsecurity.com/ru-ru/research/trending-vulnerabilities/CVE-2025-24054
- Research or write-up: https://www.rapid7.com/db/vulnerabilities/microsoft-windows-cve-2025-24054
Vulnerability databases and vendor advisories (12)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://access.redhat.com/security/cve/cve-2025-24054
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2025-6336
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-6v67-599p-fprc
- Vulnerability database or vendor advisory: https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2025-24054
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-24054
- Vulnerability database or vendor advisory: https://vicarius.io/vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microsoft-detection-script
- Vulnerability database or vendor advisory: https://vicarius.io/vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microsoft-mitigation-script
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24054
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202503-1251
- Vulnerability database or vendor advisory: https://www.tenable.com/cve/CVE-2025-24054
- Vulnerability database or vendor advisory: https://www.vicarius.io/vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microsoft-detection-script
- Vulnerability database or vendor advisory: https://www.vicarius.io/vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microsoft-mitigation-script
316 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.623
very likely to be attacked soon - VEDAS
- 0.985
strong exploit evidence - On CISA KEV
- Yes, since 2025-04-17
- Detection rule
- None yet
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Microsoft Windows 10 Version 1507 | from 10.0.10240.0 before 10.0.10240.20947 | Not stated |
| Microsoft Windows 10 Version 1607 | from 10.0.14393.0 before 10.0.14393.7876 | Not stated |
| Microsoft Windows 10 Version 1809 | from 10.0.17763.0 before 10.0.17763.7009 | Not stated |
| Microsoft Windows 10 Version 21H2 | from 10.0.19044.0 before 10.0.19044.5608 | Not stated |
| Microsoft Windows 10 Version 22H2 | from 10.0.19045.0 before 10.0.19045.5608 | Not stated |
| Microsoft Windows 11 version 22H2 | from 10.0.22621.0 before 10.0.22621.5039 | Not stated |
| Microsoft Windows 11 version 22H3 | from 10.0.22631.0 before 10.0.22631.5039 | Not stated |
| Microsoft Windows 11 Version 23H2 | from 10.0.22631.0 before 10.0.22631.5039 | Not stated |
| Microsoft Windows 11 Version 24H2 | from 10.0.26100.0 before 10.0.26100.3476 | Not stated |
| Microsoft Windows Server 2008 R2 Service Pack 1 | from 6.1.7601.0 before 6.1.7601.27618 | Not stated |
| Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) | from 6.1.7601.0 before 6.1.7601.27618 | Not stated |
| Microsoft Windows Server 2012 | from 6.2.9200.0 before 6.2.9200.25368 | Not stated |
| Microsoft Windows Server 2012 (Server Core installation) | from 6.2.9200.0 before 6.2.9200.25368 | Not stated |
| Microsoft Windows Server 2012 R2 | from 6.3.9600.0 before 6.3.9600.22470 | Not stated |
| Microsoft Windows Server 2012 R2 (Server Core installation) | from 6.3.9600.0 before 6.3.9600.22470 | Not stated |
| Microsoft Windows Server 2016 | from 10.0.14393.0 before 10.0.14393.7876 | Not stated |
| Microsoft Windows Server 2016 (Server Core installation) | from 10.0.14393.0 before 10.0.14393.7876 | Not stated |
| Microsoft Windows Server 2019 | from 10.0.17763.0 before 10.0.17763.7009 | Not stated |
| Microsoft Windows Server 2019 (Server Core installation) | from 10.0.17763.0 before 10.0.17763.7009 | Not stated |
| Microsoft Windows Server 2022 | from 10.0.20348.0 before 10.0.20348.3328 | Not stated |
3 more products are listed in the CVE record.
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: microsoft windows_10_1507, microsoft windows_10_1607, microsoft windows_10_1809, microsoft windows_10_21h2, microsoft windows_10_22h2, microsoft windows_11_22h2, microsoft windows_11_23h2, microsoft windows_11_24h2, microsoft windows_server_2008, microsoft windows_server_2012.
How to fix it
Fixed versions stated in the CVE record: 10.0.10240.20947, 10.0.14393.7876, 10.0.17763.7009, 10.0.19044.5608, 10.0.19045.5608, 10.0.22621.5039, 10.0.22631.5039, 10.0.26100.3476, 6.1.7601.27618, 6.2.9200.25368, 6.3.9600.22470, 10.0.20348.3328 and others.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor guidance:
- NTLM Hash Disclosure Spoofing Vulnerability (vendor-advisory, patch)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Vendor advisories and patches
- NTLM Hash Disclosure Spoofing Vulnerability (vendor-advisory, patch)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24054 (government-resource)
Other references
- http://seclists.org/fulldisclosure/2025/Apr/28
- https://www.vicarius.io/vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microsoft-detection-script
- https://www.vicarius.io/vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microsoft-mitigation-script
- https://www.exploit-db.com/exploits/52478
- https://www.exploit-db.com/exploits/52480
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.