Microsoft's eighth Patch Tuesday of 2026 is one of the largest cumulative update releases we have seen from Redmond: 398 CVEs patched in a single cycle, with 42 rated Critical, 355 rated Important, and one rated Moderate. Buried in that volume are three zero-day vulnerabilities — including at least one confirmed to be exploited in the wild before patches were available, headlined by CVE-2026-68820. (Note: Tenable's count omits two MITRE-assigned CVEs — CVE-2026-6726 and CVE-2026-6727 — so the true remediation scope is even larger than the headline number.)
If you run a Windows estate — and statistically, you do — this is an all-hands patch cycle. The affected product list reads like a map of the modern enterprise attack surface: .NET (all flavors), Active Directory Certificate Services (AD CS), Azure Active Directory, Azure CycleCloud, Azure Monitor Agent, Azure Storage Explorer, Capability Access Management Service (camsvc), Desktop Window Manager, Dynamics Business Central, GitHub Copilot and Visual Studio Code, AMD Zen platform components, and more. That span — from kernel-adjacent OS components to cloud agents to developer tooling — means there is no segment of a typical environment that escapes this release untouched.
When a zero-day is confirmed exploited in the wild, the math changes. You are no longer racing a hypothetical attacker; you are racing adversaries who already have working tradecraft and a head start measured in weeks. Assume exploitation attempts against unpatched systems will begin — or already have.
What We Know
- Total CVEs addressed: 398 (per Tenable's count, excluding CVE-2026-6726 and CVE-2026-6727)
- Severity breakdown: 42 Critical / 355 Important / 1 Moderate / 0 Low
- Zero-days: 3, including CVE-2026-68820
- Exploitation status: At least one zero-day was a security issue exploited in the wild prior to patch availability — this is not a theoretical risk
Affected Product Surface
The August 2026 release touches an unusually broad set of components. Defenders should inventory exposure across:
| Category | Affected Components |
|---|---|
| Runtime / Developer | .NET, .NET Core, .NET Framework, GitHub Copilot, Visual Studio Code |
| Identity & Access | Azure Active Directory, Active Directory Certificate Services (AD CS), Capability Access Management Service (camsvc) |
| Cloud / Hybrid Agents | Azure Monitor Agent, Azure CycleCloud, Azure Storage Explorer, Azure Attestation |
| Core OS | Desktop Window Manager (dwm.exe), Application Information Services |
| Hardware/Platform | AMD Zen platform components |
| Business Apps | Dynamics Business Central |
The presence of AD CS and camsvc on this list deserves special attention. AD CS has been a favorite escalation and persistence target for years (the ESC1–ESC8 technique family), and any new CVE in the certificate services stack warrants immediate review of your PKI posture. Similarly, camsvc — the Capability Access Management Service — brokers access to sensitive device capabilities, making privilege escalation bugs in that service high-value for post-compromise operators.
Why the Zero-Day Matters
A vulnerability exploited before a patch exists means one thing for defenders: patching is necessary but not sufficient. If threat actors had operational access to CVE-2026-68820 before August 2026, any system that was internet-exposed, hosting high-value identities, or reachable by an initial-access broker may already be compromised. Your remediation plan must include a retroactive hunt window — go back at least 30–60 days before the patch release and look for post-exploitation behavior, not just the exploit itself.
Exploitation Chain: Defender's Perspective
Without full technical disclosure on the exploited zero-day, defenders should model the most probable post-exploitation behaviors against the affected components:
- Initial execution of the exploit against the vulnerable component (system service, runtime, or cloud agent).
- Privilege escalation or code execution in a SYSTEM/service context — the dominant pattern for exploited Windows zero-days is a low-privileged trigger yielding elevated code execution.
- Post-exploitation staging: SYSTEM-level processes spawning command interpreters, dropping payloads to temp/Public directories, or establishing persistence via services, scheduled tasks, or Run keys.
- Identity attacks where AD CS or Azure AD components are involved: rogue certificate enrollment, token theft, or cloud agent abuse.
This model is what drives the detection content below. We are hunting the behavioral exhaust of exploitation, not version strings — that work belongs to your vulnerability scanner.
Detection & Response
The detections below focus on high-fidelity, low-noise behaviors associated with post-exploitation of Windows system services and identity components implicated in this release. Deploy them with a retroactive hunt window of at least 60 days.
Sigma Rules
---
title: SYSTEM Service Process Spawning Command Interpreter
description: Detects critical Windows services (including components patched in August 2026 such as camsvc and Desktop Window Manager) spawning command interpreters or scripting engines — a common post-exploitation pattern following service-level privilege escalation via a zero-day.
references:
- https://www.tenable.com/blog/microsofts-august-2026-patch-tuesday-addresses-398-cves-cve-2026-68820
- https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/08/12
status: experimental
id: 8f2b6c41-3a9e-4d77-b512-6e9c0f4a2d81
tags:
- attack.execution
- attack.privilege_escalation
- attack.t1059
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\camsvc.exe'
- '\dwm.exe'
- '\svchost.exe'
ParentCommandLine|contains:
- 'camsvc'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\wscript.exe'
- '\cscript.exe'
- '\mshta.exe'
- '\rundll32.exe'
condition: all of selection_*
falsepositives:
- Rare; legitimate service management tools may spawn shells interactively, but services spawning interpreters non-interactively is highly anomalous
level: high
---
title: Suspicious AD CS Certificate Enrollment Activity Following Exploitation
description: Detects certificate template or enrollment abuse indicators associated with AD CS exploitation (ESC-style abuse), relevant given AD CS patches in the August 2026 release. Looks for certutil or certreq execution by non-administrative accounts requesting certificates.
references:
- https://www.tenable.com/blog/microsofts-august-2026-patch-tuesday-addresses-398-cves-cve-2026-68820
- https://attack.mitre.org/techniques/T1649/
author: Security Arsenal
date: 2026/08/12
status: experimental
id: 3c7a9d12-8b4f-4e61-a905-2f8d1b6e7c93
tags:
- attack.credential_access
- attack.t1649
logsource:
category: process_creation
product: windows
detection:
selection_img:
Image|endswith:
- '\certreq.exe'
- '\certutil.exe'
selection_args:
CommandLine|contains:
- '-enroll'
- '-submit'
- '-retrieve'
- 'CertificateTemplate'
filter_admins:
User|contains:
- 'S-1-5-18'
- 'S-1-5-19'
- 'S-1-5-20'
condition: selection_img and selection_args and not filter_admins
falsepositives:
- Automated enrollment tooling (MDM, SCEP/NDES integrations) — baseline and exclude known service accounts
level: medium
---
title: Azure Monitor Agent or Cloud Agent Spawning Unexpected Child Process
description: Detects Azure Monitor Agent (AMA) and related Azure hybrid agent processes spawning shells or downloaders, a post-exploitation pattern consistent with cloud agent vulnerabilities patched in August 2026.
references:
- https://www.tenable.com/blog/microsofts-august-2026-patch-tuesday-addresses-398-cves-cve-2026-68820
- https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/08/12
status: experimental
id: 61d4e8a0-2c5b-4f39-87a1-9e0d4c6b3f27
tags:
- attack.execution
- attack.t1059
logsource:
category: process_creation
product: windows
detection:
selection_parent:
ParentImage|endswith:
- '\MonAgentCore.exe'
- '\MonAgentHost.exe'
- '\MonAgentLauncher.exe'
selection_child:
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
- '\bitsadmin.exe'
- '\curl.exe'
- '\wget.exe'
- '\certutil.exe'
condition: selection_parent and selection_child
falsepositives:
- Extension deployments via AMA can legitimately invoke scripts — validate against Azure Arc/AMA extension deployment logs before escalating
level: high
KQL Hunt (Microsoft Sentinel / Defender)
This query hunts for the post-exploitation pattern most relevant to this release: Windows system services and Azure agents spawning interactive tooling, with a retroactive lookback. Run it over the 60 days preceding patch deployment on any system that was unpatched during that window.
// Hunt: SYSTEM services / Azure agents spawning command interpreters (post-exploitation pattern)
// Scope: hosts pending or recently applied August 2026 cumulative updates
let Lookback = 60d;
let SuspiciousChildren = dynamic(["cmd.exe","powershell.exe","pwsh.exe","mshta.exe","wscript.exe","cscript.exe","rundll32.exe","bitsadmin.exe","certutil.exe"]);
let WatchedParents = dynamic(["camsvc.exe","dwm.exe","MonAgentCore.exe","MonAgentHost.exe","MonAgentLauncher.exe"]);
union isfuzzy=true
(DeviceProcessEvents
| where TimeGenerated >= ago(Lookback)
| where InitiatingProcessFileName in~ (WatchedParents)
| where FileName in~ (SuspiciousChildren)
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine,
FileName, ProcessCommandLine, AccountName, SHA256, InitiatingProcessId, ProcessId),
(SecurityEvent
| where TimeGenerated >= ago(Lookback)
| where EventID == 4688
| extend Parent = tostring(split(ParentProcessName, "\\")[-1]), Child = tostring(split(NewProcessName, "\\")[-1])
| where Parent in~ (WatchedParents) and Child in~ (SuspiciousChildren)
| project TimeGenerated, Computer, Parent, ParentProcessName, Child, NewProcessName,
CommandLine, SubjectAccount = TargetUserName, SubjectLogonId)
)
| sort by TimeGenerated desc
A second hunt for AD CS–specific abuse (relevant to the AD CS patches in this release) — certificate request events from unusual sources:
// Hunt: Certificate enrollment requests from non-standard accounts/hosts (AD CS abuse)
// Requires AD CS audit policy (Audit Certification Services) enabled on the CA
let Lookback = 60d;
SecurityEvent
| where TimeGenerated >= ago(Lookback)
| where EventID in (4886, 4887) // Certificate Services received a request / issued a certificate
| where TargetUserName !endswith "$" // exclude machine accounts
| summarize RequestCount = count(),
Templates = make_set(AdditionalInformation, 10),
SourceHosts = make_set(IpAddress, 10)
by TargetUserName, Computer
| where RequestCount > 5
| sort by RequestCount desc
Velociraptor VQL Hunt
Use this artifact for rapid fleet-wide triage of endpoints that were unpatched during the exposure window. It enumerates processes whose parent is a watched service binary — the same behavioral signal as the Sigma/KQL above, but executed as point-in-time forensics:
-- Security Arsenal: August 2026 Patch Tuesday post-exploitation triage
-- Find processes spawned by services/agents patched in the August 2026 release
LET watched_parents = ('camsvc.exe', 'dwm.exe', 'MonAgentCore.exe', 'MonAgentHost.exe', 'MonAgentLauncher.exe', 'svchost.exe')
LET suspicious_children = ('cmd.exe', 'powershell.exe', 'pwsh.exe', 'mshta.exe', 'rundll32.exe', 'bitsadmin.exe', 'certutil.exe', 'wscript.exe', 'cscript.exe')
LET procs = SELECT Pid, Ppid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
SELECT Pid, Name AS ChildProcess, CommandLine AS ChildCmdLine, Username,
parent.Name AS ParentProcess, parent.CommandLine AS ParentCmdLine, CreateTime
FROM procs
LET parent = SELECT Name, CommandLine FROM procs WHERE Pid = Ppid
WHERE Name =~ regex(string=suspicious_children, sep='|')
AND parent.Name =~ regex(string=watched_parents, sep='|')
Note: adapt the regex join above to your Velociraptor version — on recent releases, a JOIN over pslist() on Ppid = Pid is the cleaner construct. The analytic goal is what matters: children of watched service binaries that are interactive tooling.
Remediation & Verification Script
The following PowerShell verifies August 2026 update installation, checks pending reboot state, and inventories the highest-risk components from this release. Run it fleet-wide via your RMM, Intune, or GPO startup script.
# Security Arsenal - August 2026 Patch Tuesday verification
# Run as SYSTEM / elevated. Verifies update presence and reboot state.
$ErrorActionPreference = 'SilentlyContinue'
$report = [ordered]@{}
# 1. List hotfixes installed since August 1, 2026
$cutoff = Get-Date '2026-08-01'
$recent = Get-HotFix | Where-Object { $_.InstalledOn -ge $cutoff } |
Sort-Object InstalledOn -Descending
$report['August2026_Hotfixes'] = ($recent | ForEach-Object { "$($_.HotFixID) ($($_.InstalledOn.ToString('yyyy-MM-dd')))" }) -join '; '
# 2. Cross-check via WMI for cumulative updates (captures some updates Get-HotFix misses)
$wmi = Get-CimInstance Win32_QuickFixEngineering | Where-Object { $_.InstalledOn -ge $cutoff }
$report['WMI_UpdateCount_SinceAug2026'] = ($wmi | Measure-Object).Count
# 3. Pending reboot checks (updates staged but not active = still vulnerable)
$pendingReboot = $false
$pendingReboot = $pendingReboot -or (Test-Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\RebootPending')
$pendingReboot = $pendingReboot -or (Test-Path 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired')
$report['PendingReboot'] = $pendingReboot
# 4. Inventory high-risk components from this release
$report['ADCS_Role_Installed'] = [bool](Get-WindowsFeature AD-Certificate | Where-Object Installed)
$report['DotNet_Framework_Release'] = (Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full').Release
$report['AzureMonitorAgent_Present'] = [bool](Get-Service -Name 'AzureMonitorAgent' -ErrorAction SilentlyContinue)
# 5. Confirm the OS build is at or above the August 2026 baseline for your version
$os = Get-CimInstance Win32_OperatingSystem
$report['OS_Build'] = $os.BuildNumber
$report['OS_Version'] = $os.Version
# 6. Output for central collection
$report.GetEnumerator() | ForEach-Object { "{0} = {1}" -f $_.Key, $_.Value }
# Exit non-zero if reboot pending so RMM/SCCM flags the host as non-compliant
if ($pendingReboot) { exit 3010 } else { exit 0 }
Remediation: Prioritized Action Plan
With 398 CVEs, you cannot treat everything equally. Sequence your response:
-
Deploy the August 2026 cumulative updates immediately for internet-facing and identity infrastructure. Domain controllers, AD CS servers, Azure AD Connect hosts, and any system running the Azure Monitor Agent are priority one. Obtain updates via Windows Update, WSUS, or the Microsoft Update Catalog.
-
Patch the exploited zero-day (CVE-2026-68820) before anything else. A vulnerability exploited in the wild gets queued ahead of higher-CVSS-but-theoretical issues. Confirm installation and reboot completion — an installed-but-unrebooted patch leaves the vulnerable code running.
-
Check CISA KEV. Given confirmed in-the-wild exploitation, expect one or more of these CVEs to land in the CISA Known Exploited Vulnerabilities catalog with a mandated remediation deadline for federal agencies — treat that deadline as your own SLA regardless of sector.
-
Hunt retroactively. Run the detections above across a 60-day pre-patch window on any system that was exposed. Patching closes the door; it does not evict anyone already inside. Look for persistence (new services, scheduled tasks, Run keys), unexpected accounts, and rogue certificates issued by your AD CS infrastructure.
-
Developer tooling is in scope. GitHub Copilot and Visual Studio Code appear in this release. Developer workstations hold source code, signing keys, and cloud credentials — push the VS Code update through your software management channel and verify extension auto-update is functioning.
-
Cloud agent hygiene. Azure Monitor Agent updates flow through Azure extension auto-upgrade where enabled. Audit which VMs/Arc servers have auto-upgrade disabled and patch them explicitly — these agents run with elevated privileges on every enrolled host.
-
Review AD CS posture independently of this CVE. Audit certificate templates for overly permissive enrollment rights, verify CA audit logging (Audit Certification Services) is enabled so the KQL above has data to work with, and alert on certificate issuance outside approved workflows.
-
Track the two MITRE-assigned stragglers. CVE-2026-6726 and CVE-2026-6727 were excluded from Tenable's count — monitor the MSRC Security Update Guide and the Tenable analysis for their final status so they don't fall through your patch compliance reporting.
Bottom Line
August 2026 is not a routine Patch Tuesday. Three zero-days — one already weaponized — inside a 398-CVE release means your patch window should be measured in days, not weeks, and your response must pair deployment with retroactive hunting. Patch fast, verify reboots, hunt backward 60 days, and treat identity infrastructure (AD CS, Azure AD, cloud agents) as ground zero.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.