Skip to content
Server Security Center
KEVmedium6.5

CVE-2025-24054: Microsoft Windows NTLM Hash Disclosure Spoofing

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-04-17.

CVSS v3.1 (CVE record)
6.5
medium
EPSS (exploit probability, 30 days)
62%
higher than 99.2% of all CVEs
Added to CISA KEV
2025-04-17
US federal due date 2025-05-08
Automatable (CISA SSVC)
no
technical impact: partial

CVE-2025-24054 explained

CVE-2025-24054 is an NTLM hash disclosure spoofing vulnerability in Microsoft Windows. It stems from external control of a file name or path in Windows NTLM, letting an unauthorized attacker perform spoofing over a network. CISA lists it as known exploited, so affected Windows clients and servers should be patched promptly.

Impact

An unauthenticated attacker on the network can cause disclosure of sensitive information, as reflected by the high confidentiality impact, which the vulnerability name ties to NTLM hashes. The attack has low complexity but requires user interaction. Integrity and availability are not affected. CISA rates it as not automatable with partial technical impact. Attackers are known to exploit it in the wild; ransomware use is unknown.

Who is affected

Multiple Windows versions are affected. Examples: Windows 10 Version 1507 before 10.0.10240.20947, 1607 before 10.0.14393.7876, 1809 before 10.0.17763.7009, 21H2 before 10.0.19044.5608, 22H2 before 10.0.19045.5608; Windows 11 22H2 before 10.0.22621.5039, 22H3 and 23H2 before 10.0.22631.5039, 24H2 before 10.0.26100.3476; Windows Server 2008 R2 SP1 (including Server Core) before 6.1.7601.27618; Windows Server 2012 before 6.2.9200.25368. Each listed fixed build contains the fix. Further products are listed on the page.

Written with AI from the data on this page and checked against it automatically.

Official description

External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network.

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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Windows 10 Version 150732-bit, x64
    Affected
    • < 10.0.10240.20947
    Fixed in
    • 10.0.10240.20947
  • Microsoft Windows 10 Version 160732-bit, x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows 10 Version 180932-bit, x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows 10 Version 21H232-bit, ARM64, x64
    Affected
    • < 10.0.19044.5608
    Fixed in
    • 10.0.19044.5608
  • Microsoft Windows 10 Version 22H232-bit, ARM64, x64
    Affected
    • < 10.0.19045.5608
    Fixed in
    • 10.0.19045.5608
  • Microsoft Windows 11 version 22H2ARM64, x64
    Affected
    • < 10.0.22621.5039
    Fixed in
    • 10.0.22621.5039
  • Microsoft Windows 11 version 22H3ARM64
    Affected
    • < 10.0.22631.5039
    Fixed in
    • 10.0.22631.5039
  • Microsoft Windows 11 Version 23H2x64
    Affected
    • < 10.0.22631.5039
    Fixed in
    • 10.0.22631.5039
  • Microsoft Windows 11 Version 24H2ARM64, x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476
  • Microsoft Windows Server 2008 R2 Service Pack 1x64
    Affected
    • < 6.1.7601.27618
    Fixed in
    • 6.1.7601.27618
Show 13 more products
  • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation)x64
    Affected
    • < 6.1.7601.27618
    Fixed in
    • 6.1.7601.27618
  • Microsoft Windows Server 2012x64
    Affected
    • < 6.2.9200.25368
    Fixed in
    • 6.2.9200.25368
  • Microsoft Windows Server 2012 (Server Core installation)x64
    Affected
    • < 6.2.9200.25368
    Fixed in
    • 6.2.9200.25368
  • Microsoft Windows Server 2012 R2x64
    Affected
    • < 6.3.9600.22470
    Fixed in
    • 6.3.9600.22470
  • Microsoft Windows Server 2012 R2 (Server Core installation)x64
    Affected
    • < 6.3.9600.22470
    Fixed in
    • 6.3.9600.22470
  • Microsoft Windows Server 2016x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows Server 2016 (Server Core installation)x64
    Affected
    • < 10.0.14393.7876
    Fixed in
    • 10.0.14393.7876
  • Microsoft Windows Server 2019x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows Server 2019 (Server Core installation)x64
    Affected
    • < 10.0.17763.7009
    Fixed in
    • 10.0.17763.7009
  • Microsoft Windows Server 2022x64
    Affected
    • < 10.0.20348.3328
    Fixed in
    • 10.0.20348.3328
  • Microsoft Windows Server 2022, 23H2 Edition (Server Core installation)x64
    Affected
    • < 10.0.25398.1486
    Fixed in
    • 10.0.25398.1486
  • Microsoft Windows Server 2025x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476
  • Microsoft Windows Server 2025 (Server Core installation)x64
    Affected
    • < 10.0.26100.3476
    Fixed in
    • 10.0.26100.3476

How to fix it

  • Update to the fixed version for your product:
    • Microsoft Windows 10 Version 1507: 10.0.10240.20947
    • Microsoft Windows 10 Version 1607: 10.0.14393.7876
    • Microsoft Windows 10 Version 1809: 10.0.17763.7009
    • Microsoft Windows 10 Version 21H2: 10.0.19044.5608
    • Microsoft Windows 10 Version 22H2: 10.0.19045.5608
    • Microsoft Windows 11 version 22H2: 10.0.22621.5039
    Fixed versions for 17 more products are in the table above.
  • Vendor advisory: msrc.microsoft.com/update-guide/vulnerability/CVE-2025-24054
  • CISA's deadline for US federal agencies: 2025-05-08 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Install the Microsoft security update that brings each system to at least the fixed build listed for its Windows version.
  2. Prioritize patching, since CISA lists this vulnerability as known exploited; US federal agencies had a due date of 2025-05-08.
  3. Follow the Microsoft advisory for any additional mitigations, and discontinue use of products where mitigations are unavailable, per CISA's required action.
  4. Make users aware that exploitation requires user interaction, and treat untrusted files and network locations with caution.
  5. Review systems for signs of compromise, such as unexpected outbound NTLM authentication attempts.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Partial – limited control or information

Weakness: CWE-73 External Control of File Name or Path

Questions about CVE-2025-24054

Is CVE-2025-24054 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-04-17. Whether it has been used in ransomware campaigns is unknown.
Does an attacker need credentials?
No. The attack works over a network without privileges, but it requires a user to interact. The main impact is disclosure of confidential information. Integrity and availability are not affected.
Which Windows build fixes it on Windows 11 24H2?
Windows 11 Version 24H2 is fixed in build 10.0.26100.3476. Earlier builds are affected.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.