Microsoft's August 2026 Patch Tuesday fixes about 400 vulnerabilities, including 42 rated Critical and three zero-days. One of those zero-days, CVE-2026-68820, is already being exploited in the wild and gives a local attacker a path to SYSTEM privileges. Microsoft shipped the updates on August 11, 2026, and the U.S. Cybersecurity and Infrastructure Security Agency has since added the exploited flaw to its Known Exploited Vulnerabilities catalog.
Patch Tuesday counts are always large, but the story here is priority. One flaw is under active attack and two more were public before a fix existed, so the order you patch in matters more than the headline number.
Key takeaways
- Microsoft fixed roughly 400 vulnerabilities, including 42 rated Critical (counts vary by source: Tenable tallies 398 CVEs, SecurityWeek 421).
- Three zero-days were addressed: one exploited in the wild and two publicly disclosed before patches.
- CVE-2026-68820 (Windows AFD for WinSock, CVSS 7.0) is the actively exploited flaw and lets a local attacker reach SYSTEM.
- CISA added CVE-2026-68820 to its KEV catalog, setting a remediation deadline for U.S. federal civilian agencies.
- Elevation of privilege and remote code execution were the two largest vulnerability categories this month.
Affected
What Microsoft fixed in August 2026
Microsoft's August 2026 Patch Tuesday addresses about 400 vulnerabilities across Windows and its wider product range. Of those, 42 are rated Critical and three are zero-days. Microsoft shipped the updates on August 11, 2026.
Exact totals depend on who's counting. Tenable tallies 398 CVEs, BleepingComputer reports 400 flaws, and SecurityWeek counts 421. These gaps are normal for Patch Tuesday: vendors differ on whether to include republished advisories, Chromium-based Edge issues, and third-party CVEs. The headline number is less useful than the risk ranking underneath it.
The two largest categories this month were elevation of privilege and remote code execution. Per Tenable, elevation of privilege made up about 41 percent of fixes and remote code execution about 27 percent.
Counts vary by source
Totals range from 398 to 421 across outlets. Treat the number as approximate and focus on the exploited and Critical flaws.
The zero-day under active attack: CVE-2026-68820
CVE-2026-68820 is an elevation-of-privilege flaw in the Windows Ancillary Function Driver for WinSock (afd.sys). It carries a CVSS score of 7.0 and is rated Important. Microsoft's assessment marks it as exploited in the wild.
The flaw is a local privilege escalation. An attacker who already has a foothold on a machine can use it to elevate to SYSTEM, the highest privilege level on Windows. Flaws like this rarely start an attack on their own. They are the second stage, turning limited access from phishing or a stolen credential into full control of the host.
Check Point researchers Moshe Marelus and David Driker are credited with reporting the flaw. Check Point has linked the observed exploitation to the North Korea-aligned Lazarus group. That attribution comes from a single research source, so treat it as reported rather than settled until more vendors corroborate it.
Patch this one first
CVE-2026-68820 is the only August flaw confirmed as exploited in the wild, and CISA has added it to its Known Exploited Vulnerabilities catalog.
The two publicly disclosed zero-days
Two more zero-days were public before Microsoft shipped a fix. Neither is confirmed as exploited yet, but public disclosure narrows the gap between discovery and attack.
CVE-2026-62832 is an elevation-of-privilege flaw in the Windows User Profile Service, with a CVSS score of 7.8. A successful attacker could gain administrator privileges. Microsoft assessed it as more likely to be exploited, so it deserves attention alongside the actively attacked flaw.
CVE-2026-72971 is a tampering vulnerability in the Windows Container Isolation FS Filter Driver (unionfs.sys), with a CVSS score of 5.5. Microsoft rated its exploitation as unlikely, which puts it lower in the queue but still worth patching in the same cycle.
Who needs to act
The updates span Windows, Windows Server, Microsoft Office, SharePoint, and Exchange Server, so most Microsoft environments are in scope. The priority is any Windows endpoint or server where the exploited WinSock flaw applies.
Managed service providers and IT teams that run monthly patch cycles should confirm the August updates reached every managed device, not just the ones people log into daily. Neglected servers and dormant machines are where privilege-escalation flaws sit unpatched the longest.
U.S. federal civilian agencies have a firm deadline. Because CVE-2026-68820 is in CISA's KEV catalog, those agencies must remediate it within the timeframe CISA sets. Private organizations aren't bound by that deadline, but KEV listing is a strong signal to move fast.
What to patch first
Apply the August 2026 cumulative updates through your normal channel: Windows Update, WSUS, Microsoft Update Catalog, or your patch-management tool. If you stage patches, don't wait a full cycle on the exploited flaw.
Rank the work by risk, not by CVE number:
- CVE-2026-68820 first: exploited in the wild, reaches SYSTEM, and listed in CISA KEV.
- CVE-2026-62832 next: Microsoft assessed it as more likely to be exploited, and it grants administrator privileges.
- The 42 Critical flaws: work through the remote code execution issues that apply to your environment.
- The rest of the cumulative update, including CVE-2026-72971, on your normal cycle.
What to watch next
Watch for exploitation reports on the two publicly disclosed flaws, especially CVE-2026-62832, which Microsoft flagged as more likely to be exploited. Public disclosure without active attacks can change quickly once proof-of-concept code circulates.
Also watch for corroboration of the Lazarus attribution. Right now that link rests on Check Point's research. Independent confirmation from Microsoft Threat Intelligence or another vendor would firm it up. Until then, the safe read is that CVE-2026-68820 is exploited in the wild, with attribution still developing.
Timeline
Impact & actions
The August 2026 updates close about 400 flaws, one of which is already being used in attacks to gain SYSTEM-level control of Windows hosts.
Security: One zero-day is exploited in the wild; two more were public before a patch existed, shortening the window before broader attacks.
Recommended actions · High urgency
- 1Apply the August 2026 cumulative updates across all managed Windows devices and servers.
- 2Prioritize CVE-2026-68820, which is exploited in the wild and listed in CISA KEV.
- 3Patch CVE-2026-62832 next, given Microsoft's more likely to be exploited assessment.
- 4Confirm coverage on dormant or infrequently used machines, not just daily-driver endpoints.
Technical details
- CVEs
- CVE-2026-68820, CVE-2026-62832, CVE-2026-72971
- CVSS
- 7
- Exploitation
- Exploited in the wild
- Attack vector
- Local privilege escalation; an authenticated local attacker can elevate to SYSTEM (CVE-2026-68820).
- Affected versions
- Supported Windows and Windows Server releases per Microsoft's advisory
- Patched versions
- August 2026 cumulative updates
Mitigations
- Install the August 2026 Microsoft security updates.
- Prioritize the exploited flaw CVE-2026-68820 on all affected hosts.
Response
Vendor
Authorities
Customer guidance
Apply the August 2026 updates and prioritize the exploited WinSock flaw. Confirm patch coverage across all managed devices.
FAQ
How many vulnerabilities did Microsoft fix in August 2026?
About 400. Counts vary by source: Tenable tallies 398 CVEs, BleepingComputer reports 400 flaws, and SecurityWeek counts 421. The differences come from how each vendor counts republished and third-party advisories. Of these, 42 are rated Critical.
Which August 2026 zero-day is being exploited?
CVE-2026-68820, an elevation-of-privilege flaw in the Windows Ancillary Function Driver for WinSock. It carries a CVSS score of 7.0 and lets a local attacker elevate to SYSTEM. Microsoft marked it as exploited in the wild, and CISA added it to its KEV catalog.
What are the other two zero-days?
CVE-2026-62832 is a Windows User Profile Service elevation-of-privilege flaw (CVSS 7.8) that Microsoft assessed as more likely to be exploited. CVE-2026-72971 is a Windows Container Isolation FS Filter Driver tampering flaw (CVSS 5.5) rated exploitation unlikely. Both were publicly disclosed before patches shipped.
Which fix should I apply first?
Prioritize CVE-2026-68820. It's the only one confirmed as exploited in the wild, it reaches SYSTEM privileges, and it's in CISA's KEV catalog. Patch CVE-2026-62832 next, then work through the 42 Critical flaws and the rest of the cumulative update.
Is the Lazarus attribution confirmed?
Not fully. Check Point researchers reported CVE-2026-68820 and linked the exploitation to the North Korea-aligned Lazarus group. That attribution comes from a single research source for now, so treat it as reported rather than confirmed until other vendors corroborate it.
The bottom line
Microsoft's August 2026 Patch Tuesday fixed about 400 vulnerabilities, including 42 Critical and three zero-days. One, CVE-2026-68820, is exploited in the wild and now sits in CISA's KEV catalog.
What happens next
What to do






