Skip to content
All posts

CVE-2026-70229: AD DS Remote Code Execution, What to Do

November 21, 2026 · Team PlayCISO
TL;DR · the short version

CVE-2026-70229 is a remote code execution vulnerability in Windows Active Directory Domain Services (AD DS). Microsoft fixed it in the October 2026 Patch Tuesday updates (13 October 2026), rates it Critical, CVSS 3.1 8.1 (attack complexity high), and says an unauthenticated attacker could send a specially crafted packet over the network to run code, with no user interaction. Microsoft rates it "Exploitation More Likely" but, as of its 4 November revision, lists it as not exploited and not publicly disclosed; CISA had not added it to the KEV catalog as of 20 November. A third-party alert (Positive Technologies dbugs) reports a public proof of concept on GitHub; PlayCISO has not verified it, and defenders should not run unvetted exploit code. Affected: Windows Server 2012 to 2025 and Windows 10 and 11. Microsoft lists no workaround: install the October 2026 or later updates, domain controllers first.

Put it into practice
Put domain controller patches at the top of the queue
Rank CVE-2026-70229 against the rest of your backlog by exposure, exploitability and what the asset controls.
Open the vulnerability prioritizer

CVE-2026-70229 is a Critical remote code execution flaw in Windows Active Directory Domain Services (AD DS), the role that runs your domain controllers. Microsoft fixed it in the October 2026 Patch Tuesday updates on 13 October 2026 and says an unauthenticated attacker could run code by sending "a specially crafted packet to an affected service over the network", with no user interaction. Microsoft lists it as not exploited and rates it "Exploitation More Likely". A third-party alert now says a proof of concept is public; that claim is unverified. If your domain controllers do not yet have the October 2026 or later update, install it now.

Who this is for: CISOs, Windows and identity teams, and anyone who owns patching for domain controllers.

Checked on 21 November 2026 against Microsoft's Security Update Guide, NVD, the CVE.org record and the CISA KEV catalog. PlayCISO is not affiliated with Microsoft. We did not open, download or run the GitHub repository the alert links to, and we do not link it.

Confirmed vs not yet known

  • Confirmed by Microsoft: remote code execution in AD DS caused by incorrect authorization (CWE-863); Critical; CVSS 3.1 base 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H); no authentication or user interaction needed; fixed on 13 October 2026 for every listed Windows version; "Exploitation More Likely".
  • Microsoft's status flags (revision 1.1, 4 November 2026): Exploited: No. Publicly disclosed: No.
  • CISA: not in the Known Exploited Vulnerabilities catalog as of the 20 November 2026 catalog. CISA's assessment on 13 October 2026 (published on the CVE record): exploitation "none", automatable "no", technical impact "total".
  • Claimed, not verified: a Positive Technologies dbugs alert (PT-2026-112320) says a proof of concept has been published on GitHub. We have not verified it. Action1 lists a public proof of concept as "not confirmed".
  • Not known: which AD DS protocol or port is involved; whether machines that are not domain controllers can be reached; any workaround (Microsoft lists none); any confirmed attack in the wild.

What Microsoft says

Microsoft's entry is short. The description reads: "Incorrect authorization in Active Directory Domain Services allows an unauthorized attacker to execute code over a network." On how it could be exploited: "An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network. Successful exploitation could allow the attacker to execute code on the target system. No authentication or user interaction is required."

The score is 8.1 rather than 9.8 because Microsoft rates the attack complexity as high. Its explanation: "Exploitation requires specific conditions, including particular network configurations and timing conditions, and has only been observed in limited scenarios. This means an attacker cannot reliably exploit the issue in all environments." Microsoft does not say what those conditions are, and the same entry marks the flaw as not exploited. Do not read "high complexity" as "safe to wait": the impact on a domain controller is the whole domain.

Affected versions and updates

Microsoft lists these products and updates (October 2026). Any later cumulative update for the same version also contains the fix.

Windows versionUpdateFixed build
Windows Server 2025 (incl. Server Core)KB512664610.0.26100.33650
Windows Server 2022 (incl. Server Core)KB512665510.0.20348.5761
Windows Server 2019 (incl. Server Core), Windows 10 1809KB512665110.0.17763.9376
Windows Server 2016 (incl. Server Core), Windows 10 1607KB512686810.0.14393.9612
Windows Server 2012 R2 (incl. Server Core)KB5126836 (Monthly Rollup)6.3.9600.23470
Windows Server 2012 (incl. Server Core)KB51268356.2.9200.26434
Windows 10 21H2 and 22H2KB512665710.0.19044.7807 / 10.0.19045.7807
Windows 11 23H2KB512665310.0.22631.7652
Windows 11 24H2, 25H2, 26H2KB512764810.0.26100.9711 / 10.0.26200.9711 / 10.0.26300.9711
Windows 11 26H1KB512764610.0.28000.3231

Microsoft marks a reboot as required. If you still run Windows Server 2012 or 2012 R2 domain controllers, check that you are actually receiving these updates.

Useful next, if this was relevant to you

Showing 1 of 3: CISO Readiness Scorecard

What security leaders should do this week

  1. Patch domain controllers first. Confirm every domain controller is on the October 2026 or later cumulative update (compare the build number with the table above). Ask for evidence per server, not a dashboard percentage.
  2. Find every domain controller. Forgotten DCs in test forests, branch offices, DR sites and cloud VMs are the ones that miss patch cycles. Run nltest /dclist:<domain> or query AD for computer objects in the Domain Controllers OU, and reconcile with your asset inventory.
  3. Then patch everything else. Microsoft lists Windows 10 and 11 as affected too and does not say they are unreachable. Fold them into the normal ring, without waiting for the next cycle.
  4. Reduce who can reach a DC. Microsoft gives no workaround, so until patching is done, restrict network access to domain controllers to the systems that need it and keep them off any internet-facing segment.
  5. Watch domain controllers closely. Alert on unexpected processes started by lsass.exe or other DC services, new services, new accounts in privileged groups and unusual replication requests. Make sure DC security logs reach your SIEM and are kept.
  6. Do not run unvetted PoC code. Fake "proof of concept" repositories for new Windows CVEs regularly carry malware aimed at the people who download them. Do not clone or run one on a workstation or in a lab connected to your network. Verify patch status with build numbers, not with an exploit.
  7. Track the status. Re-check Microsoft's entry and the KEV catalog. If CISA adds it to KEV or Microsoft changes "Exploited" to Yes, treat any unpatched DC as a likely incident.

Timeline

DateEventSource
3 Aug 2026CVE-2026-70229 reserved by Microsoft.CVE.org
13 Oct 2026Published and fixed in the October 2026 Patch Tuesday updates; Critical, CVSS 8.1, "Exploitation More Likely".Microsoft
13 Oct 2026CISA's SSVC assessment on the CVE record: exploitation none, automatable no, technical impact total.CVE.org (CISA ADP)
28 Oct 2026NVD analysis completed (status Analyzed).NVD
4 Nov 2026Microsoft revision 1.1: acknowledgement updated ("informational change only"); still Exploited: No, Publicly disclosed: No.Microsoft
20 Nov 2026Not in the CISA KEV catalog (catalog version 2026.11.20).CISA KEV catalog (checked via its JSON feed)
Nov 2026Positive Technologies dbugs alert PT-2026-112320 says a proof of concept was found on GitHub. Not verified by PlayCISO.Third-party alert (not linked)

Where the reports disagree

  • Is there a public exploit? The dbugs alert says yes. Microsoft's entry still says the flaw was not publicly disclosed, and Action1 lists a public proof of concept as not confirmed. We could not confirm one from a source we trust.
  • Score: some third-party summaries quote 9.8. Microsoft, the CVE issuer, scores it 8.1 because of the high attack complexity.

Was Microsoft breached?

No. This is a vulnerability in a Windows component that Microsoft fixed in October 2026. Our Microsoft Breach Index entry lists it as a vulnerability, not a breach.

Practise the decision

Run CVE-2026-70229 through the SSVC calculator with your own exposure, check its status any time in the KEV checker, and use Time to Domain Admin to show the board why a domain controller flaw jumps the queue.

Frequently asked questions

What is CVE-2026-70229?

A remote code execution vulnerability in Windows Active Directory Domain Services (AD DS), the Windows role that runs domain controllers. Microsoft describes it as "Incorrect authorization in Active Directory Domain Services allows an unauthorized attacker to execute code over a network" (CWE-863, incorrect authorization). Microsoft rates it Critical with a CVSS 3.1 base score of 8.1.

When was CVE-2026-70229 patched?

In the October 2026 Patch Tuesday updates, released on 13 October 2026. Microsoft lists a security update for every affected Windows version, from Windows Server 2012 to Windows Server 2025 and from Windows 10 1607 to Windows 11 26H2. Any October 2026 or later cumulative update for your version includes the fix.

Is CVE-2026-70229 being exploited?

Not according to Microsoft. As of its latest revision (4 November 2026), Microsoft's entry says "Exploited: No" and "Publicly disclosed: No", and rates it "Exploitation More Likely". CISA had not added it to the Known Exploited Vulnerabilities (KEV) catalog as of the 20 November 2026 catalog. CISA's own assessment on 13 October 2026 recorded exploitation as "none".

Is there a public proof of concept for CVE-2026-70229?

A third-party vulnerability alert (Positive Technologies' dbugs, PT-2026-112320) reports that a proof of concept has been published on GitHub. PlayCISO has not verified that claim and does not link the repository. Microsoft still lists the flaw as not publicly disclosed, and Action1 lists a public proof of concept as not confirmed. Fake "PoC" repositories for new Windows vulnerabilities are a known way to spread malware to researchers and defenders, so do not download or run unvetted exploit code.

Does an attacker need credentials to exploit CVE-2026-70229?

No. Microsoft says "An unauthenticated attacker could exploit this vulnerability by sending a specially crafted packet to an affected service over the network" and that "No authentication or user interaction is required." The attack complexity is high: Microsoft says exploitation "requires specific conditions, including particular network configurations and timing conditions".

Why is the CVSS score 8.1 and not 9.8?

Because Microsoft scores the attack complexity as high (AC:H): an attacker cannot reliably exploit it in every environment. The rest of the vector is the worst case: network attack, no privileges, no user interaction, and high impact to confidentiality, integrity and availability. Some third-party summaries quote 9.8; Microsoft, which issued the CVE, says 8.1.

Which Windows versions are affected by CVE-2026-70229?

Microsoft lists Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 (including Server Core installations), Windows 10 versions 1607, 1809, 21H2 and 22H2, and Windows 11 versions 23H2, 24H2, 25H2, 26H1 and 26H2. The fixed builds include 10.0.17763.9376 (Server 2019), 10.0.20348.5761 (Server 2022) and 10.0.26100.33650 (Server 2025).

Do only domain controllers need the patch?

Microsoft lists client versions of Windows as affected too, and does not say whether the flaw can be reached on a machine that is not a domain controller. Patch everything, but patch domain controllers first: they hold the AD DS role and the keys to the whole domain.

Is there a workaround for CVE-2026-70229?

Microsoft's entry lists no mitigation or workaround. The fix is the security update. Until it is installed, limit which networks can reach your domain controllers and watch them closely.

Was Microsoft breached?

No. This is a vulnerability in a Windows component that Microsoft fixed in October 2026, not a breach of Microsoft.

Sources

Put domain controller patches at the top of the queue
Rank CVE-2026-70229 against the rest of your backlog by exposure, exploitability and what the asset controls.
Open the vulnerability prioritizer
Take this with you
Confirmed vs not yet known · What Microsoft says · Affected versions and updates · What security leaders should do this week · Timeline · Where the reports disagree

Ready to practise the decisions these articles describe?

Run your first Cyber War Room free →

Pro