dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Jul 2022.
Windows 10 1507Operating system · Microsoft

CVE-2022-26925

MEDIUM · 5.9 CVSS v3.1 Published 2022-05-10
Fix available
A fix is available. Upgrade to 10.0.10240.19297 / 10.0.14393.5125 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Windows LSA Spoofing Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Windows Local Security Authority (LSA) spoofing vulnerability. The LSA subsystem handles authentication and security policy enforcement in Windows. A successful exploit could allow an attacker to spoof the LSA, potentially authenticating as a different user or system. The medium severity (5.9) suggests the attack requires some level of access or user interaction.

MitigationApply the relevant Microsoft security updates for CVE-2022-26925 to all affected Windows systems, including domain controllers and servers running Windows LSA.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.19297
Windows 10 1607Operating system
Affected:< 10.0.14393.5125
Windows 10 1809Operating system
Affected:< 10.0.17763.2928
Windows 10 1909Operating system
Affected:< 10.0.18363.2274
Windows 10 20h2Operating system
Affected:< 10.0.19042.1706
Windows 10 21h1Operating system
Affected:< 10.0.19043.1706
Windows 10 21h2Operating system
Affected:< 10.0.19044.1706
Windows 11 21h2Operating system
Affected:< 10.0.22000.675

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Windows version
    Run 'winver' from command prompt or use PowerShell: [System.Environment]::OSVersion.Version or check the 'winver' dialog showing version and build number
    Affected if The displayed version and build number is lower than any of the following: Windows 10 1507 build 10240.19297, Windows 10 1607 build 14393.5125, Windows 10 1809 build 17763.2928, Windows 10 1909 build 18363.2274, Windows 10 20h2 build 19042.1706, Windows 10 21h1 build 19043.1706, Windows 10 21h2 buil
  2. Confirm Windows edition and build via systeminfo
    Run 'systeminfo' from command prompt and look at 'OS Name', 'OS Version', and 'Build Number' entries
    Affected if The version matches an affected Windows 10 or Windows 11 release and the build number is below the corresponding threshold for that release as listed in the affected versions
  3. Verify if security update KB5011570 is installed
    Run PowerShell command 'Get-HotFix -Id KB5011570' or open Control Panel > Programs > View installed updates and search for KB5011570
    Affected if The hotfix KB5011570 is NOT listed as installed on the system
  4. Check domain-joined status
    Run 'whoami /groups' and look for 'Domain Users' or similar domain groups, or check System Properties for 'Domain: [domain name]' entry
    Affected if The system is joined to an Active Directory domain (vulnerability primarily impacts domain environments)

A system is affected if it runs any of the listed Windows 10 or Windows 11 versions below the specified build thresholds AND lacks the KB5011570 security update, particularly if the system is joined to a Windows domain.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.19297 / 10.0.14393.5125 / 10.0.17763.2928 or later
Fixed in 10.0.10240.1929710.0.14393.512510.0.17763.2928
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply the relevant Microsoft security updates for CVE-2022-26925 to all affected Windows systems, including domain controllers and servers running Windows LSA.

Recommended fix High confidence

Upgrade to the appropriate cumulative security update: Windows 10 1507 to build 10.0.10240.19297+, Windows 10 1607 to build 10.0.14393.5125+, Windows 10 1809 to build 10.0.17763.2928+, Windows 10 1909 to build 10.0.18363.2274+, Windows 10 20H2 to build 10.0.19042.1706+, Windows 10 21H1 to build 10.0

  1. Open Settings on the Windows system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest cumulative security update
  4. Verify the update installed successfully by checking the installed updates list
  5. Confirm the OS build number matches or exceeds the fixed version for your Windows release (10.0.10240.19297 for 1507, 10.0.14393.5125 for 1607, 10.0.17763.2928 for 1809, 10.0.18363.2274 for 1909, 10.0.19042.1706 for 20H2, 10.0.19043.1706 for 21H1, 10.0.19044.1706 for 21H2, or 10.0.22000.675 for Windows 11 21H2)
  6. Restart the system if prompted to complete the update installation
Caveat Standard Windows cumulative security updates typically have minimal risk; ensure critical data is backed up before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26925 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-26925 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data