# CVE-2022-26923: Microsoft Active Directory Domain Services Privilege Escalation

> Attackers can elevate privileges in Active Directory Domain Services, requiring Microsoft Windows patches.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Yes, since 18 Aug 2022 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 May 2022
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-j9xf-76vv-4wcg

## What is CVE-2022-26923?

CVE-2022-26923 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 10 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Active Directory Domain Services Elevation of Privilege Vulnerability

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2022-26923?

It affects 14 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 1909, Microsoft Windows 10 20h2, Microsoft Windows 10 21h1, Microsoft Windows 10 21h2, Microsoft Windows 11 21h2, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022.

## How do I fix CVE-2022-26923?

Apply the vendor's patch. US federal agencies must fix it by 8 Sep 2022.

## Is CVE-2022-26923 being exploited?

Yes. Attackers have exploited CVE-2022-26923 in the wild since at least 18 Aug 2022.

Public exploit code:

- 检测域内常见一把梭漏洞，包括：NoPac、ZeroLogon、CVE-2022-26923、PrintNightMare (github_poc): https://github.com/evilashz/PIGADVulnScanner
- The vulnerability allowed a low-privileged user to escalate privileges to domain administrator in a default Active Directory environment with the Active Directory Certificate Services (AD CS) server role installed. (github_poc): https://github.com/LudovicPatho/CVE-2022-26923_AD-Certificate-Services
- A powershell poc to load and automatically run Certify and Rubeus from memory. (github_poc): https://github.com/lsecqt/CVE-2022-26923-Powershell-POC
- Walkthrough on the exploitation of CVE-2022-26923, a vulnerability in AD Certificate Services (github_poc): https://github.com/r1skkam/TryHackMe-CVE-2022-26923
- A proof of concept exploiting CVE-2022-26923. (github_poc): https://github.com/Gh-Badr/CVE-2022-26923
- Exploitation de CVE-2022-26923 (github_poc): https://github.com/Eliasdekiniweek/CVE-2022-26923

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-26923 and fix it if it is affected.

What it is: CVE-2022-26923 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 10 May 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2022-26923 in the wild since at least 18 Aug 2022.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-26923/ (Markdown: https://insights.sbomify.com/CVE-2022-26923/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-26923
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-26923
- OSV: https://osv.dev/vulnerability/CVE-2022-26923

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-26923/
Summaries are generated and may contain mistakes; the official description above is the record.