CVE-2022-26925Known exploitationPublic exploitNetwork attack vector

Domain takeover via anonymous LSARPC authentication coercion

Published May 10, 2022 · Updated Oct 21, 2025

Spoofing in Microsoft Windows LSA allows remote attackers to coerce a domain controller into NTLM authentication through LSARPC. An anonymously callable LSARPC method accepts an attacker-controlled network path and initiates outbound NTLM authentication to that destination. Network access to LSARPC is sufficient; relaying the coerced authentication to a suitable service can grant control of the Windows domain.

CVSS severity8.1
High
EPSS probability10.72%
Next 30 days · Sep 16, 2026
Known exploitationReported
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Spoofing in Microsoft Windows LSA allows remote attackers to coerce a domain controller into NTLM authentication through LSARPC. An anonymously callable LSARPC method accepts an attacker-controlled network path and initiates outbound NTLM authentication to that destination. Network access to LSARPC is sufficient; relaying the coerced authentication to a suitable service can grant control of the Windows domain.

The record

CVE
CVE-2022-26925
Published
May 10, 2022
Updated
Oct 21, 2025
Vendor
Microsoft
Product
Windows 10 Version 1507
Classifications
CWE-306, T1187
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. May 10, 2022CVE publishedPublication date reported by the CVE source.
  2. Jul 1, 2022Exploitation reportedCISA Known Exploited Vulnerabilities catalog listing
  3. Jul 6, 2022Exploitation reportedReported active exploitation of the LSARPC vector
  4. Oct 21, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=10.0.10240.0 <10.0.10240.19297

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Microsoft · Windows 10 Version 1507version=10.0.10240.0 <10.0.10240.19297
Microsoft · Windows Server 2019version=10.0.17763.0 <10.0.17763.2928
Microsoft · Windows 7version=6.1.0 <6.1.7601.25954
Microsoft · Windows 10 Version 21H1version=10.0.0 <10.0.19043.1706
Microsoft · Windows 10 Version 1909version=10.0.0 <10.0.18363.2274
Microsoft · Windows 8.1version=6.3.0 <6.3.9600.20371
Microsoft · Windows Server 2016 (Server Core installation)version=10.0.14393.0 <10.0.14393.5125
Microsoft · Windows 11 version 21H2version=10.0.0 <10.0.22000.675
Microsoft · Windows Server 2012 (Server Core installation)version=6.2.9200.0 <6.2.9200.23714
Microsoft · Windows Server 2012version=6.2.9200.0 <6.2.9200.23714
Microsoft · Windows 10 Version 21H2version=10.0.19043.0 <10.0.19043.1706
Microsoft · Windows Server 2016version=10.0.14393.0 <10.0.14393.5125
Microsoft · Windows Server 2008 R2 Service Pack 1version=6.1.7601.0 <6.1.7601.25954
Microsoft · Windows 10 Version 20H2version=10.0.0 <10.0.19042.1706
Microsoft · Windows Server 2008 R2 Service Pack 1 (Server Core installation)version=6.1.7601.0 <6.1.7601.25954
Microsoft · Windows Server 2012 R2 (Server Core installation)version=6.3.9600.0 <6.3.9600.20371
Microsoft · Windows Server 2019 (Server Core installation)version=10.0.17763.0 <10.0.17763.2928
Microsoft · Windows 7 Service Pack 1version=6.1.0 <6.1.7601.25954
Microsoft · Windows Server version 20H2version=10.0.0 <10.0.19042.1706
Microsoft · Windows 10 Version 1607version=10.0.14393.0 <10.0.14393.5125
Microsoft · Windows Server 2008 Service Pack 2version=6.0.6003.0 <6.0.6003.21481
Microsoft · Windows Server 2022version=10.0.20348.0 <10.0.20348.707
Microsoft · Windows 10 Version 1809version=10.0.0 <10.0.17763.2928; version=10.0.17763.0 <10.0.17763.2928
Microsoft · Windows Server 2012 R2version=6.3.9600.0 <6.3.9600.20371
Microsoft · Windows Server 2008 Service Pack 2 (Server Core installation)version=6.0.6003.0 <6.0.6003.21481

Published CVSS scores

8.1Microsoft CorporationCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
5.9NIST NVDCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationReported
Public exploitPublished

Weakness, pattern, technique

CWE-306Missing Authentication for Critical Function
T1187Forced Authentication

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo