CriticalCVE-2022-26925

    Windows LSA Spoofing Vulnerability (CVE-2022-26925)

    Published In CISA KEV since Sources: SingCERT, CVE.org

    What is affected, what to do

    Windows LSA Spoofing Vulnerability

    The vulnerability is being actively exploited; treat it as a priority. Update Microsoft Windows 10 Version 1809 to version 10.0.17763.2928, Microsoft Windows Server 2019 to version 10.0.17763.2928, Microsoft Windows Server 2019 (Server Core installation) to version 10.0.17763.2928. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows 10 Version 1809 lt 10.0.17763.0..10.0.17763.2928
    • Microsoft Windows Server 2019 lt 10.0.17763.0..10.0.17763.2928
    • Microsoft Windows Server 2019 (Server Core installation) lt 10.0.17763.0..10.0.17763.2928
    • Microsoft Windows 10 Version 1909 lt 10.0.0..10.0.18363.2274
    • Microsoft Windows 10 Version 21H1 lt 10.0.0..10.0.19043.1706
    • Microsoft Windows Server 2022 lt 10.0.20348.0..10.0.20348.707
    • Microsoft Windows 10 Version 20H2 lt 10.0.0..10.0.19042.1706
    • Microsoft Windows Server version 20H2 lt 10.0.0..10.0.19042.1706
    • Microsoft Windows 11 version 21H2 lt 10.0.0..10.0.22000.675
    • Microsoft Windows 10 Version 21H2 lt 10.0.19043.0..10.0.19043.1706
    • Microsoft Windows 10 Version 1507 lt 10.0.10240.0..10.0.10240.19297
    • Microsoft Windows 10 Version 1607 lt 10.0.14393.0..10.0.14393.5125
    • Microsoft Windows Server 2016 lt 10.0.14393.0..10.0.14393.5125
    • Microsoft Windows Server 2016 (Server Core installation) lt 10.0.14393.0..10.0.14393.5125
    • Microsoft Windows 7 lt 6.1.0..6.1.7601.25954
    • Microsoft Windows 7 Service Pack 1 lt 6.1.0..6.1.7601.25954
    • Microsoft Windows 8.1 lt 6.3.0..6.3.9600.20371
    • Microsoft Windows Server 2008 Service Pack 2 lt 6.0.6003.0..6.0.6003.21481
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) lt 6.0.6003.0..6.0.6003.21481
    • Microsoft Windows Server 2008 R2 Service Pack 1 lt 6.1.7601.0..6.1.7601.25954
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) lt 6.1.7601.0..6.1.7601.25954
    • Microsoft Windows Server 2012 lt 6.2.9200.0..6.2.9200.23714
    • Microsoft Windows Server 2012 (Server Core installation) lt 6.2.9200.0..6.2.9200.23714
    • Microsoft Windows Server 2012 R2 lt 6.3.9600.0..6.3.9600.20371
    • Microsoft Windows Server 2012 R2 (Server Core installation) lt 6.3.9600.0..6.3.9600.20371
    Fixed in
    • Microsoft Windows 10 Version 1809 10.0.17763.2928
    • Microsoft Windows Server 2019 10.0.17763.2928
    • Microsoft Windows Server 2019 (Server Core installation) 10.0.17763.2928
    • Microsoft Windows 10 Version 1909 10.0.18363.2274
    • Microsoft Windows 10 Version 21H1 10.0.19043.1706
    • Microsoft Windows Server 2022 10.0.20348.707
    • Microsoft Windows 10 Version 20H2 10.0.19042.1706
    • Microsoft Windows Server version 20H2 10.0.19042.1706
    • Microsoft Windows 11 version 21H2 10.0.22000.675
    • Microsoft Windows 10 Version 21H2 10.0.19043.1706
    • Microsoft Windows 10 Version 1507 10.0.10240.19297
    • Microsoft Windows 10 Version 1607 10.0.14393.5125
    • Microsoft Windows Server 2016 10.0.14393.5125
    • Microsoft Windows Server 2016 (Server Core installation) 10.0.14393.5125
    • Microsoft Windows 7 6.1.7601.25954
    • Microsoft Windows 7 Service Pack 1 6.1.7601.25954
    • Microsoft Windows 8.1 6.3.9600.20371
    • Microsoft Windows Server 2008 Service Pack 2 6.0.6003.21481
    • Microsoft Windows Server 2008 Service Pack 2 (Server Core installation) 6.0.6003.21481
    • Microsoft Windows Server 2008 R2 Service Pack 1 6.1.7601.25954
    • Microsoft Windows Server 2008 R2 Service Pack 1 (Server Core installation) 6.1.7601.25954
    • Microsoft Windows Server 2012 6.2.9200.23714
    • Microsoft Windows Server 2012 (Server Core installation) 6.2.9200.23714
    • Microsoft Windows Server 2012 R2 6.3.9600.20371
    • Microsoft Windows Server 2012 R2 (Server Core installation) 6.3.9600.20371

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    8.1

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v3

    8.1

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: SingCERT, CVE.org

    10.5 %

    EPSS score

    Elevated — model estimates 10-50% exploitation likelihood.

    Source: FIRST EPSS, percentile 95.8

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    214.65 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: CSA/SingCERT How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    8.1 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    8.1
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    10.5 %
    Elevated — model estimates 10-50% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    95.8
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 4 February 2025
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-306

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This flaw lets an unauthenticated network attacker force a domain controller to authenticate via NTLM. Relayed to AD CS (the ESC8 pattern), that turns into full domain compromise within minutes. The high attack complexity mainly reflects the need for a relay position, but public tooling makes this reliable in typical Windows estates running AD CS. CISA does not flag ransomware use, yet exploitation likelihood is in the upper tier of all CVEs. Treat it as critical if you run AD CS Web Enrollment, lack SMB/LDAP signing or have flat networks, since domain admin is the pivot point for nearly every ransomware chain. Estates with tiered DC access and hardened AD CS can handle it at standard high priority.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Patch domain controllers first: Deploy the May 2022 Microsoft security update or later to every DC. Minimum builds from the advisory context are 10.0.14393.5125 (1607/Server 2016 base), 10.0.17763.2928 (1809/Server 2019 base), 10.0.10240.19297 (1507), 10.0.18363.2274 (1909), 10.0.19042.1706 (20H2), 10.0.19043.1706 (21H1/21H2) and 10.0.22000.675 (Win 11 21H2). Other server editions also have a vendor patch; look up the exact build in the vendor advisory.
      • Check follow-up updates: The May 2022 rollup caused certificate-based authentication failures on some DCs. Check the vendor advisory for subsequent fix releases and validate on a test DC before broad rollout. Do not roll back to an unpatched baseline.
      • Inventory relay targets: Identify every host that accepts inbound NTLM, especially AD CS Web Enrollment (/certsrv), CES/CEP, LDAP without signing and SMB without signing. These are where a coerced DC authentication gets relayed.
      • Lock down AD CS now: On the IIS hosting /certsrv and CES, set Extended Protection for Authentication (EPA) to Required and enforce HTTPS only. Remove the NTLM provider, or disable Web Enrollment entirely where it is not needed.
      • Compromise assessment: Review recent weeks for certificate requests and NTLM logons made as DC machine accounts (see Detection rules). If you find any, revoke the certificates, reset krbtgt twice and reset the DC machine account passwords.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Restrict RPC to DCs (TCP 135, 139, 445 and the dynamic RPC range 49152-65535) to admin and server tiers. Client, guest and OT VLANs and VPN pools should not reach DC RPC freely. Block outbound SMB/HTTP from DCs to client segments.
      • RPC filters (endpoint hardening): Use netsh rpc filter to restrict LSARPC (UUID 12345778-1234-abcd-ef00-0123456789ab) and EFSRPC (UUID c681d488-d850-11d0-8c52-00c04fd90f7e) to authenticated, authorised callers. Stage the filters in audit first.
      • Restrict NTLM via GPO: On DCs, set "Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers" to Audit all, then to Deny all with an exception list. Also audit incoming NTLM.
      • Signing and channel binding: Enforce SMB signing on all servers. Set LDAP server signing to Require and LDAP channel binding to Always, which neutralises relays to LDAP and SMB.
      • IAM / least privilege: Add privileged accounts to Protected Users so they cannot use NTLM. Audit certificate templates for over-broad enrollment rights, and minimise Domain Computers enrollment on templates with the Client Authentication EKU.
      • IPS/NDR: Enable Suricata/Zeek detections for DCERPC binds to the LSARPC/EFSRPC UUIDs from non-admin subnets. Alert on NTLM-over-HTTP to AD CS hosts where the authenticating principal is a DC machine account.

    3. Runbook step 3

      Detection rules

      • DC machine account NTLM logon to a non-DC: Look for Security 4624 with LogonType 3 and AuthenticationPackageName NTLM, where TargetUserName is a DC account ($) and the source IP is not a DC. KQL: SecurityEvent | where EventID==4624 and AuthenticationPackageName=="NTLM" and TargetUserName in (dc_accounts) and IpAddress !in (dc_ips)
      • Certificate issued for a DC from an odd source: Look for AD CS events 4886/4887 where the requester is a DC machine account and the request came via Web Enrollment. These are typically followed by a 4768 with PreAuthType 16 (PKINIT) for that DC account from a non-DC IP.
      • Named-pipe access to lsarpc/efsrpc: Enable Detailed File Share auditing and watch Event 5145 with RelativeTargetName lsarpc, efsrpc or lsass from ANONYMOUS LOGON or non-admin hosts. Sigma: EventID: 5145 AND RelativeTargetName|contains: [lsarpc, efsrpc] AND SubjectUserName: ANONYMOUS LOGON.
      • Network telemetry: Look for Zeek dce_rpc.log entries with endpoint in (lsarpc, efsrpc) and unusual operations (e.g. EfsRpcOpenFileRaw, LsarOpenPolicy) from client subnets. A tell-tale sign is the DC opening SMB/HTTP back to the same source IP shortly afterwards.
      • NTLM audit log: Review Microsoft-Windows-NTLM/Operational (8001/8004) for outbound NTLM from DCs. Any outbound NTLM from a DC to a workstation-class host warrants immediate triage.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    Windows LSA Spoofing Vulnerability

    Source: CSA/SingCERT, NVD (NIST), CISA KEV Catalog, CVE.org (MITRE), cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 10 Version 1507
    • 10.0.10240.0 – < 10.0.10240.19297
    • 10.0.10240.19297
    MicrosoftWindows 10 Version 1607
    • 10.0.14393.0 – < 10.0.14393.5125
    • 10.0.14393.5125
    MicrosoftWindows 10 Version 1809
    • 10.0.17763.0 – < 10.0.17763.2928
    • 10.0.17763.2928
    MicrosoftWindows 10 Version 1909
    • 10.0.0 – < 10.0.18363.2274
    • 10.0.18363.2274
    MicrosoftWindows 10 Version 20H2
    • 10.0.0 – < 10.0.19042.1706
    • 10.0.19042.1706
    MicrosoftWindows 10 Version 21H1
    • 10.0.0 – < 10.0.19043.1706
    • 10.0.19043.1706
    MicrosoftWindows 10 Version 21H2
    • 10.0.19043.0 – < 10.0.19043.1706
    • 10.0.19043.1706
    MicrosoftWindows 11 version 21H2
    • 10.0.0 – < 10.0.22000.675
    • 10.0.22000.675
    MicrosoftWindows 7
    • 6.1.0 – < 6.1.7601.25954
    • 6.1.7601.25954
    MicrosoftWindows 7 Service Pack 1
    • 6.1.0 – < 6.1.7601.25954
    • 6.1.7601.25954
    MicrosoftWindows 8.1
    • 6.3.0 – < 6.3.9600.20371
    • 6.3.9600.20371
    MicrosoftWindows Server 2008 R2 Service Pack 1
    • 6.1.7601.0 – < 6.1.7601.25954
    • 6.1.7601.25954
    MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)
    • 6.1.7601.0 – < 6.1.7601.25954
    • 6.1.7601.25954
    MicrosoftWindows Server 2008 Service Pack 2
    • 6.0.6003.0 – < 6.0.6003.21481
    • 6.0.6003.21481
    MicrosoftWindows Server 2008 Service Pack 2 (Server Core installation)
    • 6.0.6003.0 – < 6.0.6003.21481
    • 6.0.6003.21481
    MicrosoftWindows Server 2012
    • 6.2.9200.0 – < 6.2.9200.23714
    • 6.2.9200.23714
    MicrosoftWindows Server 2012 (Server Core installation)
    • 6.2.9200.0 – < 6.2.9200.23714
    • 6.2.9200.23714
    MicrosoftWindows Server 2012 R2
    • 6.3.9600.0 – < 6.3.9600.20371
    • 6.3.9600.20371
    MicrosoftWindows Server 2012 R2 (Server Core installation)
    • 6.3.9600.0 – < 6.3.9600.20371
    • 6.3.9600.20371
    MicrosoftWindows Server 2016
    • 10.0.14393.0 – < 10.0.14393.5125
    • 10.0.14393.5125
    MicrosoftWindows Server 2016 (Server Core installation)
    • 10.0.14393.0 – < 10.0.14393.5125
    • 10.0.14393.5125
    MicrosoftWindows Server 2019
    • 10.0.17763.0 – < 10.0.17763.2928
    • 10.0.17763.2928
    MicrosoftWindows Server 2019 (Server Core installation)
    • 10.0.17763.0 – < 10.0.17763.2928
    • 10.0.17763.2928
    MicrosoftWindows Server 2022
    • 10.0.20348.0 – < 10.0.20348.707
    • 10.0.20348.707
    MicrosoftWindows Server version 20H2
    • 10.0.0 – < 10.0.19042.1706
    • 10.0.19042.1706

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_10_1507—
    Windowsmicrosoftwindows_10_1607—
    Windowsmicrosoftwindows_10_1809—
    Windowsmicrosoftwindows_10_1909—
    Windowsmicrosoftwindows_10_20h2—
    Windowsmicrosoftwindows_10_21h1—
    Windowsmicrosoftwindows_10_21h2—
    Windowsmicrosoftwindows_11_21h2—
    Windowsmicrosoftwindows_7—
    Windowsmicrosoftwindows_8.1—
    Windowsmicrosoftwindows_rt_8.1—
    Windowsmicrosoftwindows_server_2008r2
    Windowsmicrosoftwindows_server_2008—
    Windowsmicrosoftwindows_server_2012r2
    Windowsmicrosoftwindows_server_2012—
    Windowsmicrosoftwindows_server_2016—
    Windowsmicrosoftwindows_server_2019—
    Windowsmicrosoftwindows_server_2022—
    Windowsmicrosoftwindows_server_20h2—

    Weakness classes (CWE)

    • CWE-306Missing Authentication for Critical Function

      Base

      The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

      Entry at MITRE CWE-306

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    CSA/SingCERTActive Exploitation of Windows LSA Spoofing Vulnerability (opens in a new tab)CSA/SingCERTactively exploited

    References & sources

    • Microsoft Security Update GuideWindows LSA Spoofing VulnerabilityVendor advisory, Patch, Vendor advisory
    • portal.msrc.microsoft.comen-US/security-guidance/advisory/CVE-2022-26925x_refsource_MISC, x_transferred, Patch, Vendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2022-26925government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2022-26925
    <a href="https://intel.neosec.eu/en/cve/CVE-2022-26925"><img src="https://intel.neosec.eu/badge/cve/CVE-2022-26925.svg?lang=en" alt="CVE-2022-26925 – NEOSEC Intel" height="20"></a>