CVE-2026-21249: Windows NTLM Spoofing Vulnerability

Published Feb 10, 2026
·
Updated

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

Affected Software

80 affected componentsFixes available
Microsoft Windows 10 1607<10.0.14393.8868
Microsoft Windows 10 1607<10.0.14393.8868
Microsoft Windows 10 1809<10.0.17763.8389
Microsoft Windows 10 1809<10.0.17763.8389
Microsoft Windows 10 21h2<10.0.19044.6937
Microsoft Windows 10 21h2<10.0.19044.6937
Microsoft Windows 10 21h2<10.0.19044.6937
Microsoft Windows 10 22h2<10.0.19045.6937
Microsoft Windows 10 22h2<10.0.19045.6937
Microsoft Windows 10 22h2<10.0.19045.6937
Microsoft Windows 11 23h2<10.0.22631.6649
Microsoft Windows 11 23h2<10.0.22631.6649
Microsoft Windows 11 24h2<10.0.26100.7781
Microsoft Windows 11 24h2<10.0.26100.7781
Microsoft Windows 11 25h2<10.0.26200.7781
Microsoft Windows 11 25h2<10.0.26200.7781
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.8868
Microsoft Windows Server 2019<10.0.17763.8389
Microsoft Windows Server 2022<10.0.20348.4711
Microsoft Windows Server 2022 23h2<10.0.25398.2149
Microsoft Windows Server 2025<10.0.26100.32313
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2016
Microsoft Windows 10=1607
Microsoft Windows Server 2016
Microsoft Windows Server 2025
Microsoft Windows 11=24H2
Microsoft Windows 10=1607
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows 11=23H2
Microsoft Windows 11=24H2
Microsoft Windows 11=25H2
Microsoft Windows 11=25H2
Microsoft Windows Server 2025
Microsoft Windows 10=22H2
Microsoft Windows 11=23H2
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows Server 2019
Microsoft Windows 10=1809
Microsoft Windows 10=1809
Microsoft Windows Server 2022
Microsoft Windows Server 2019
Microsoft Windows 11=26H1
Microsoft Windows 11=26H1
Microsoft Windows Server 2022
Microsoft Windows Server 2016<10.0.14393.8868
10.0.14393.8868
Microsoft Windows Server 2016<10.0.14393.8868
10.0.14393.8868
Microsoft Windows 11=23H2
10.0.22631.6649
Microsoft Windows 11=24H2
10.0.26100.784010.0.26100.7781
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.2149
10.0.25398.2149
Microsoft Windows Server 2012 R2<6.3.9600.23022
6.3.9600.23022
Microsoft Windows 10=1607
10.0.14393.8868
Microsoft Windows Server 2012 R2<6.3.9600.23022
6.3.9600.23022
Microsoft Windows 11=24H2
10.0.26100.784010.0.26100.7781
Microsoft Windows 10=22H2
10.0.19045.6937
Microsoft Windows 10=1607
10.0.14393.8868
Microsoft Windows Server 2025<10.0.26100.32370, <10.0.26100.32313
10.0.26100.3237010.0.26100.32313
Microsoft Windows 11=23H2
10.0.22631.6649
Microsoft Windows 10=22H2
10.0.19045.6937
Microsoft Windows 11=25H2
10.0.26200.784010.0.26200.7781
Microsoft Windows 11=25H2
10.0.26200.784010.0.26200.7781
Microsoft Windows 10=21H2
10.0.19044.6937
Microsoft Windows 10=22H2
10.0.19045.6937
Microsoft Windows Server 2025<10.0.26100.32370, <10.0.26100.32313
10.0.26100.3237010.0.26100.32313
Microsoft Windows 10=21H2
10.0.19044.6937
Microsoft Windows Server 2022<10.0.20348.4773, <10.0.20348.4711
10.0.20348.477310.0.20348.4711
Microsoft Windows Server 2022<10.0.20348.4773, <10.0.20348.4711
10.0.20348.477310.0.20348.4711
Microsoft Windows Server 2019<10.0.17763.8389
10.0.17763.8389
Microsoft Windows Server 2019<10.0.17763.8389
10.0.17763.8389
Microsoft Windows 10=21H2
10.0.19044.6937
Microsoft Windows 10=1809
10.0.17763.8389
Microsoft Windows 11=26H1
10.0.28000.1575
Microsoft Windows 11=26H1
10.0.28000.1575
Microsoft Windows 10=1809
10.0.17763.8389

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.8868Patch KB5075999
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.6649Patch KB5075941
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.7840Fixed in 10.0.26100.7781Patch KB5077212
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.2149Patch KB5075897
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23022Patch KB5075970
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.6937Patch KB5075912
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.7840Fixed in 10.0.26200.7781Patch KB5077212
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.32370Fixed in 10.0.26100.32313Patch KB5075942
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.6937Patch KB5075912
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.8389Patch KB5075904
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.4773Fixed in 10.0.20348.4711Patch KB5075943
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.1575Patch KB5077179

Event History

Feb 10, 2026
CVE Published
via Microsoft·04:00 PM
Data Sourced
via Microsoft·04:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·04:00 PM
Affected Software
Updated
via Microsoft·04:00 PM
Description
CVE Published
via MITRE·05:51 PM
Data Sourced
via MITRE·05:51 PM
DescriptionSeverity
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-21249?

CVE-2026-21249 is considered a critical vulnerability due to its potential for unauthorized access and local spoofing attacks.

2

How do I fix CVE-2026-21249?

To fix CVE-2026-21249, apply the relevant security updates provided by Microsoft for your specific Windows version or edition.

3

Which versions of Windows are affected by CVE-2026-21249?

CVE-2026-21249 affects multiple Windows versions including Windows Server 2012 R2, Windows Server 2025, Windows 10, and Windows 11 among others.

4

How can I determine if my system is vulnerable to CVE-2026-21249?

You can determine vulnerability by checking if your Windows system is running an affected version and if it has the required updates installed.

5

What impact does CVE-2026-21249 have on Windows systems?

CVE-2026-21249 allows an unauthorized attacker to locally spoof accounts, potentially compromising the integrity of the system.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203