Trinetri logo
Updated monthly

Microsoft Patch Tuesday
August 2026

Microsoft's August 2026 Patch Tuesday fixes 447 vulnerabilities across Windows, Microsoft Office and Azure - 84 rated Critical, 3 publicly disclosed before the patch shipped, one already exploited in the wild. Patch CVE-2026-68820 first.

Released August 11, 2026, 10:00 PT1 actively exploited3 publicly disclosed61 KB articles to deploy

August 2026 Patch Tuesday at a glance

447
Microsoft CVEs
excl. Edge & Azure Linux
84
Critical
19% of the release
1
Actively exploited
CVE-2026-68820
3
Publicly disclosed
known before the patch
10.0
Highest CVSS
CVE-2026-69836
61
KB articles
what you actually deploy

Why this number differs from other roundups. Microsoft's August 2026 release document lists 1,645 entries. 837 are Azure Linux (Mariner) OS package updates and 361 are republished Chromium fixes for Edge - neither is a Microsoft product vulnerability. The 447 above is the real Patch Tuesday set. See the breakdown →

The numbers

What’s in this release

Where the 1,645 entries actually come from

Most roundups quote a single number. These are three unrelated release streams.

447 Microsoft products837 Azure Linux (Mariner)361 Edge (Chromium)

Severity

Microsoft channel only · 447 CVEs

August 2026 severity breakdown
Critical84
Important362
Moderate1
Low0

Impact type

What an attacker gains if it works

August 2026 impact breakdown
Elevation of Privilege190
Remote Code Execution116
Information Disclosure93
Spoofing21
Denial of Service12
Security Feature Bypass11
Tampering4

Most-affected components

Where this month’s fixes concentrate - filter by any of them in the table below

Microsoft Office SharePoint30Microsoft Office29Microsoft Office Excel28Microsoft Office Word18Windows DNS16Windows DHCP Server14Windows Win32K13Windows Telephony Service12.NET9Windows Installer9Windows Kernel9Windows NTFS8
Every patch

Browse all 1,645 entries

Sorted by risk by default: exploited first, then publicly disclosed, then severity, then CVSS. Search by CVE, title, component or KB number.

Showing 447 of 447
447 Microsoft vulnerabilities in the August 2026 Patch Tuesday, sortable by severity, CVSS and exploit status.
TitleStatusKB
ImportantCVE-2026-68820Windows Ancillary Function Driver for WinSock Elevation of Privilege VulnerabilityEoP7.0ExploitedWindows Ancillary Function Driver for WinSock5120228 +12
ImportantCVE-2026-62832Windows User Profile Service Elevation of Privilege VulnerabilityEoP7.8DisclosedMore likelyWindows User Profile Service5120228 +8
ImportantCVE-2026-69414Microsoft Defender Elevation of Privilege VulnerabilityEoP7.8DisclosedMore likelyMicrosoft Defender
ImportantCVE-2026-72971Windows Container Isolation FS Filter Driver (unionfs.sys) Tampering VulnerabilityTampering5.5DisclosedWindows Container Isolation FS Filter Driver (unionfs.sys)5121000
CriticalCVE-2026-62893Windows Deployment Services TFTP Server Remote Code Execution VulnerabilityRCE9.8More likelyWindows Deployment Services5120228 +7
CriticalCVE-2026-62823Windows DHCP Server Remote Code Execution VulnerabilityRCE8.8More likelyWindows DHCP Server5120228 +7
CriticalCVE-2026-65665Microsoft SharePoint Server Remote Code Execution VulnerabilityRCE8.8More likelyMicrosoft Office SharePoint5002893 +2
CriticalCVE-2026-69558Microsoft Partner Center Information Disclosure VulnerabilityInfo Disc.8.6More likelyMicrosoft Partner Center
ImportantCVE-2026-59124Microsoft High Performance Computing (HPC) Pack Remote Code Execution VulnerabilityRCE9.8More likelyMicrosoft High Performance Computing (HPC) Pack
ImportantCVE-2026-59133Microsoft High Performance Computing (HPC) Pack Elevation of Privilege VulnerabilityEoP8.8More likelyMicrosoft High Performance Computing (HPC) Pack
ImportantCVE-2026-63520Microsoft SharePoint Server Remote Code Execution VulnerabilityRCE8.1More likelyMicrosoft Office SharePoint5002893 +4
ImportantCVE-2026-58650Visual Studio Code Security Feature Bypass VulnerabilityBypass7.8More likelyVisual Studio Code
ImportantCVE-2026-61358Windows Accessibility Infrastructure (ATBroker.exe) Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Accessibility Infrastructure (ATBroker.exe)5120228 +9
ImportantCVE-2026-61925Windows Installer Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Installer5120228 +12
ImportantCVE-2026-61930Windows Kernel Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Kernel5120228 +10
ImportantCVE-2026-62688Windows MIDI Service Module Elevation of Privileges VulnerabilityEoP7.8More likelyWindows MIDI Service Module5120994 +2
ImportantCVE-2026-62696Windows Program Compatibility Assistant Service Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Program Compatibility Assistant Service5120228 +10
ImportantCVE-2026-62698Microsoft Digest Authentication Elevation of Privilege VulnerabilityEoP7.8More likelyMicrosoft Digest Authentication5120228 +12
ImportantCVE-2026-62712Windows Win32k Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Win32K5120228 +12
ImportantCVE-2026-62713Windows Cloud Files Mini Filter Driver Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Cloud Files Mini Filter Driver5120228 +9
ImportantCVE-2026-62721Windows User-Mode Power Service (UMPS) Elevation of Privilege VulnerabilityEoP7.8More likelyUser-Mode Power Service (UMPS)5120228 +12
ImportantCVE-2026-62735Windows HTTP.sys Elevation of Privilege VulnerabilityEoP7.8More likelyWindows HTTP.sys5120228 +12
ImportantCVE-2026-62737Windows Kernel Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Kernel5120228 +4
ImportantCVE-2026-62741Windows HTTP.sys Elevation of Privilege VulnerabilityEoP7.8More likelyWindows HTTP.sys5120228 +12
ImportantCVE-2026-62783Windows Remote Access Connection Manager Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Remote Access Connection Manager5120228 +9
Your move

What your IT team should do

The same five steps every month, in the order that reduces risk fastest.

Test the known-issue candidates

Check the Windows release health dashboard before promoting past ring 1, and have the rollback path written down before you need it. Kernel, networking and authentication fixes are the ones that historically break things.

12 Patch Management Best Practices for 2026

Verify installed state, then evidence it

Confirm the patch is actually present on each endpoint rather than trusting that "deployment succeeded". Keep the resulting report - it is the artefact auditors ask for, and reconstructing it later is far more work than capturing it now.

Patch Management: The Complete Guide

Trinetri does steps two through five automatically - detecting the 61 KB articles across every endpoint, staging them in rings, verifying installed state and producing the compliance evidence. See patch management →

Patch Tuesday FAQ

Patch Tuesday falls on the second Tuesday of every month, with updates going live at 10:00 a.m. Pacific Time. Microsoft introduced the practice in October 2003, following the Blaster worm, to cut distribution costs and give administrators a predictable cadence instead of patches arriving at random. The 10:00 a.m. timing is deliberate: it leaves a full working week to remediate before the weekend. Internally Microsoft calls it the "B" release; optional "C" and "D" preview releases follow later in the month. The next Patch Tuesday is September 8, 2026.

Microsoft fixed 447 vulnerabilities in August 2026, across Windows, Microsoft Office, Azure and Developer Tools. 84 are rated Critical, 3 were publicly disclosed before the patch shipped, and 1 was already being exploited. Note that Microsoft's release document lists 1,645 entries in total, but 837 of those are Azure Linux package updates and 361 are republished Chromium fixes for Edge, which is why other sources sometimes quote a much larger number.

Exploit Wednesday is the day after Patch Tuesday. Attackers compare the newly released patches against the previous version to locate the flaw each one fixes, then build working exploits from that difference - often within 24 to 48 hours. It is the reason the deployment window matters as much as the patch itself: every hour a Critical remote code execution fix sits undeployed is an hour of measurable exposure.

A workable target for most organisations: actively exploited vulnerabilities within 24 hours, publicly disclosed ones within 72 hours, remaining Critical fixes within seven days, and everything else within the month. CISA's Known Exploited Vulnerabilities catalogue sets binding deadlines for US federal agencies and is a reasonable benchmark for everyone else. Stage the rollout in rings rather than deploying everywhere at once, so a regression is caught on a pilot group instead of in production.

An out-of-band update is a patch released outside the monthly cycle because the risk will not wait for the next Patch Tuesday. Microsoft issues them for actively exploited flaws with no mitigation - most famously during the WannaCry outbreak in 2017, when it took the unusual step of patching versions of Windows that were already out of support.

Yes. Adobe aligned its releases with Patch Tuesday in November 2012, and both SAP's Security Patch Day and Oracle's quarterly Critical Patch Updates are coordinated to the same week. Part of the reason is defensive: staggered releases let attackers reverse-engineer one vendor's patch to find the same underlying flaw in another's still-unpatched product. For IT teams it means the second Tuesday is rarely just a Microsoft problem.

Edge is built on Chromium, so most of its security fixes originate with the Chromium project and are republished by Microsoft under their own CVE identifiers. They ship on Chromium's cadence rather than the Patch Tuesday cycle, and they are delivered by Edge's own updater rather than Windows Update. Counting the 361 Edge entries alongside Microsoft product fixes would inflate the headline number and imply work for your Windows Update rings that does not exist.

Stop the sprawl. Eliminate the guesswork.

Ready to See Autonomous Endpoint Management in Action?

Experience how Trinetri transforms endpoint chaos into clarity. Try the 30 minute demo session, our experts will walk you through how AI-powered automation, real-time visibility, and unified control can secure your entire hybrid environment, without the overhead.