cve.bz

CVE-2022-26923 (Certifried) Microsoft Active Directory Domain Services Privilege Escalation Vulnerability

8.8 highKEVExploitEPSS 84%Fix available

Known as Certifried

High (8.8) in Microsoft Active Directory. In CISA KEV since 2022-08-18. EPSS 84% estimated probability of exploitation activity in the next 30 days.

On this page
Active Directory Domain Services Elevation of Privilege Vulnerability

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
84% (unchanged from 84% a week ago; 84% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2022-08-18, due 2022-09-08
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2025-02-04. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-295 Improper Certificate Validation
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-26923 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-26923?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-26923?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-26923 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.4252
Microsoft Windows 10 Version 1809from 10.0.0 before 10.0.17763.4252
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.4252
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.4252
Microsoft Windows 10 Version 1909from 10.0.0 before 10.0.18363.2274
Microsoft Windows 10 Version 21H1from 10.0.0 before 10.0.19043.1706
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.1668
Microsoft Windows 10 Version 20H2from 10.0.0 before 10.0.19042.1706
Microsoft Windows Server version 20H2from 10.0.0 before 10.0.19042.1706
Microsoft Windows 11 version 21H2from 10.0.0 before 10.0.22000.1817
Microsoft Windows 10 Version 21H2from 10.0.19043.0 before 10.0.19043.1706
Microsoft Windows 10 Version 1507from 10.0.10240.0 before 10.0.10240.19297
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.5850
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.5850
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.5850
Microsoft Windows 8.1from 6.3.0 before 6.3.9600.20371
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.20919
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.20919

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

Attack patterns (CAPEC)

  • CAPEC-459 Creating a Rogue Certification Authority Certificate Likelihood: Medium · Severity: Very High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON