CVE-2025-24054
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? No. The vulnerability involves external control of file name or path in Windows NTLM, which is a network authentication protocol, not HTTP. Therefore, a web application firewall cannot filter or block the attack based on HTTP request patterns.
Also consider: patch
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-24054 being exploited?
Yes. CVE-2025-24054 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-24054?
CVE-2025-24054 is rated Medium with a CVSS score of 6.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-24054?
Yes. A fix has been recorded for CVE-2025-24054. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-24054 affect?
CVE-2025-24054 affects microsoft:windows_10_1507, microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, and 11 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected>= 10.0.10240.0 and < 10.0.10240.20947
- affected>= 10.0.14393.0 and < 10.0.14393.7876
- affected>= 10.0.17763.0 and < 10.0.17763.7009
- affected>= 10.0.19044.0 and < 10.0.19044.5608
- affected>= 10.0.19045.0 and < 10.0.19045.5608
- affected>= 10.0.22621.0 and < 10.0.22621.5039
- affected>= 10.0.22631.0 and < 10.0.22631.5039
- affected>= 10.0.22631.0 and < 10.0.22631.5039
- affected>= 10.0.26100.0 and < 10.0.26100.3476
- affected>= 6.1.7601.0 and < 6.1.7601.27618
- affected>= 6.1.7601.0 and < 6.1.7601.27618
- affected>= 6.2.9200.0 and < 6.2.9200.25368
- affected>= 6.3.9600.0 and < 6.3.9600.22470
- affected>= 6.3.9600.0 and < 6.3.9600.22470
- affected>= 6.2.9200.0 and < 6.2.9200.25368
- affected>= 10.0.14393.0 and < 10.0.14393.7876
- affected>= 10.0.14393.0 and < 10.0.14393.7876
- affected>= 10.0.17763.0 and < 10.0.17763.7009
- affected>= 10.0.17763.0 and < 10.0.17763.7009
- affected>= 10.0.20348.0 and < 10.0.20348.3328
- affected>= 10.0.25398.0 and < 10.0.25398.1486
- affected>= 10.0.26100.0 and < 10.0.26100.3476
- affected>= 10.0.26100.0 and < 10.0.26100.3476
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
public exploits
Public exploit code: 3 on Exploit-DB · 10 GitHub proofs of concept
- Windows 10.0.17763.7009 - spoofing vulnerability · remote · 11 Feb 2026
- windows 10/11 - NTLM Hash Disclosure Spoofing · remote · 4 Feb 2026
- Microsoft - NTLM Hash Disclosure Spoofing (library-ms) · local · 1 May 2025
- helidem/CVE-2025-24054_CVE-2025-24071-PoC · 22 ★
- basekilll/CVE-2025-24054_PoC · 4 ★
- Untouchable17/CVE-2025-24054 · 2 ★
- moften/CVE-2025-24054 · 1 ★
Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.
cisa ssvc
- exploitation
- active
- automatable
- no
- technical impact
- partial
Assessed by CISA 17 Apr 2025 (SSVC 2.0.3).
timeline
- 11 Mar 2025Published
- 17 Apr 2025Added to CISA KEV (exploited in the wild) · 36 days later
- 17 Apr 2025CISA SSVC assessment: exploitation active · 1 day later
- 18 Apr 2025First public exploit or proof of concept · same day later
- 8 May 2025CISA remediation due date (US federal agencies) · 20 days later
- 13 Feb 2026CVE record last updated · 282 days (about 9 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 262 days (about 9 months) later
- Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2025-24054
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-24054
- Linkseclists.org /fulldisclosure/2025/Apr/28
- Linkvicarius.io /vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microso
- Linkvicarius.io /vsociety/posts/cve-2025-24054-spoofing-vulnerability-in-windows-ntlm-by-microso
- Linkexploit-db.com /exploits/52478
- Linkexploit-db.com /exploits/52480
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Exploit-DB: published exploits
- PoC-in-GitHub: GitHub repositories that claim a proof of concept
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.