Windows 10 1507Operating system · Microsoft

CVE-2022-26923

HIGH · 8.8 CVSS v3.1 Published 2022-05-10

Fix available

A fix is available. Upgrade to 10.0.10240.19297 / 10.0.14393.5850 or later.

See remediation →

100/100

Remediation priority · Urgent

In the wild High EPSS Remotely reachable Zero-click Patch available

Official description

NVD · unedited

Active Directory Domain Services Elevation of Privilege Vulnerability

Technical summary

dbcve analysis · high confidence

This is a privilege escalation vulnerability in Active Directory Certificate Services (AD CS) where a low-privileged attacker can manipulate certificate request attributes to obtain a certificate valid for a higher-privilege identity (including Domain Admin), enabling full domain compromise.

MitigationApply the Microsoft security update (KB5000802 and subsequent patches) that enforces proper certificate request validation and restricts NTLM relay attacks; disable NTLM authentication on AD CS servers as an additional hardening measure.

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

Affected products & versions

NVD · CPE data

Windows 10 1507Operating system

Affected:< 10.0.10240.19297

Windows 10 1607Operating system

Affected:< 10.0.14393.5850

Windows 10 1809Operating system

Affected:< 10.0.17763.4252

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.1817

CVSS breakdown

From the vector

Attack vector: Network
Complexity: Low
Privileges: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

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

Am I affected?

dbcve checks

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

Check Windows version

Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the installed Windows version

Affected if The version falls below the patched versions listed: 10.0.10240.19297 (1507), 10.0.14393.5850 (1607), 10.0.17763.4252 (1809), 10.0.18363.2274 (1909), 10.0.19042.1706 (20h2), 10.0.19043.1706 (21h1), 10.0.19044.1706 (21h2), or 10.0.22000.1817 (Win 11 21h2)
Confirm system is a Domain Controller

Run 'Get-ADDomainController' in PowerShell or check System Properties under Computer Name to see if the machine is a Domain Controller

Affected if The system is a Domain Controller running an affected Windows version
Verify AD CS is installed

Run 'Get-WindowsFeature -Name AD-Certificate' in PowerShell on Domain Controllers, or check Server Manager for the Active Directory Certificate Services role

Affected if AD CS (Active Directory Certificate Services) is installed on the Domain Controller
Check for vulnerable certificate templates

Open 'certutil' and run 'certutil -template' or use the Certificates snap-in to examine certificate templates published by the CA; look for templates configured with dangerous settings such as 'Supply in the request' for subject name or enrollment agent privileges

Affected if The Certificate Authority publishes templates that allow requestor-specified subject names or have enrollment agent permissions configured

The environment is affected if any Domain Controller runs an affected Windows version AND has AD CS installed with vulnerable certificate template configurations.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 10.0.10240.19297 / 10.0.14393.5850 / 10.0.17763.4252 or later

Fixed in 10.0.10240.1929710.0.14393.585010.0.17763.4252

Vendor patch msrc.microsoft.com →

Interim mitigation

Apply the Microsoft security update (KB5000802 and subsequent patches) that enforces proper certificate request validation and restricts NTLM relay attacks; disable NTLM authentication on AD CS servers as an additional hardening measure.

Recommended fix High confidence

Windows 10 1507 (10.0.10240.19297), Windows 10 1607 (10.0.14393.5850), Windows 10 1809 (10.0.17763.4252), Windows 10 1909 (10.0.18363.2274), Windows 10 20H2 (10.0.19042.1706), Windows 10 21H1 (10.0.19043.1706), Windows 10 21H2 (10.0.19044.1706), or Windows 11 21H2 (10.0.22000.1817) or later

Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
Determine which Windows 10/11 release branch your system is on (1507, 1607, 1809, 1909, 20H2, 21H1, 21H2, or 11 21H2)
Navigate to Windows Update via Settings > Update & Security > Windows Update
Click 'Check for updates' and install all available updates
Alternatively, download the specific Security Update for your version from the Microsoft Update Catalog: https://catalog.update.microsoft.com/
For Windows Server running Active Directory Certificate Services, ensure the Domain Controller is updated as this vulnerability affects AD CS
After updating, verify the installed version matches or exceeds the fixed build: Windows 10 1507: 10.0.10240.19297 | Windows 10 1607: 10.0.14393.5850 | Windows 10 1809: 10.0.17763.4252 | Windows 10 1909: 10.0.18363.2274 | Windows 10 20H2: 10.0.19042.1706 | Windows 10 21H1: 10.0.19043.1706 | Windows 10 21H2: 10.0.19044.1706 | Windows 11 21H2: 10.0.22000.1817
Restart the system after the update is installed

Caveat Standard Windows update with no expected breaking changes; as a high-priority security patch, apply promptly

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement

Consultation8.0 h
Implementation16.0 h
Testing12.0 h
Review / QA4.0 h

40.0 hours of engineering $7,000

Get it fixed fast

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-26923 — 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

Primary sources

msrc.microsoft.comPatch / commit
msrc.microsoft.comPatchVendor Advisory
portal.msrc.microsoft.comPatchVendor Advisory
www.cisa.govUS Government Resource
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-26923?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

Exploited in the wildOn CISA’s known-exploited list · agencies must fix by 2022-09-08

A fix existsUpgrade to 10.0.10240.19297 / 10.0.14393.5850 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 83.0%

Affects: Windows 10 1507

Remediation

Being exploited — close it fast

Fix this in Windows 10 1507 40 hrs · High

Typical engagement from $7,000

Get it fixed fast See the full breakdown ↓

This CVE is on CISA’s actively-exploited list, so the clock is real — a vetted specialist can deliver a reviewed fix for your staging environment quickly.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References