Trinetri logo
Updated monthly

Microsoft Patch Tuesday
August 2021

Microsoft's August 2021 Patch Tuesday fixes 45 vulnerabilities across Windows, Azure and Developer Tools - 7 rated Critical, 3 publicly disclosed before the patch shipped, one already exploited in the wild. Patch CVE-2021-36948 first.

Released August 10, 2021, 10:00 PT1 actively exploited3 publicly disclosed47 KB articles to deploy

August 2021 Patch Tuesday at a glance

45
Microsoft CVEs
excl. Edge & Azure Linux
7
Critical
16% of the release
1
Actively exploited
CVE-2021-36948
3
Publicly disclosed
known before the patch
9.9
Highest CVSS
CVE-2021-26424
47
KB articles
what you actually deploy

Why this number differs from other roundups. Microsoft's August 2021 release document lists 132 entries. 74 are Azure Linux (Mariner) OS package updates and 13 are republished Chromium fixes for Edge - neither is a Microsoft product vulnerability. The 45 above is the real Patch Tuesday set. See the breakdown →

The numbers

What’s in this release

Where the 132 entries actually come from

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

45 Microsoft products74 Azure Linux (Mariner)13 Edge (Chromium)

Severity

Microsoft channel only · 45 CVEs

August 2021 severity breakdown
Critical7
Important38
Moderate0
Low0

Impact type

What an attacker gains if it works

August 2021 impact breakdown
Elevation of Privilege17
Remote Code Execution14
Information Disclosure8
Spoofing4
Denial of Service2

Most-affected components

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

Windows Services for NFS ONCRPC XDR Driver5Windows Print Spooler Components4Azure Sphere3Microsoft Dynamics 3653Windows Event Tracing3.NET Core & Visual Studio2Azure2Microsoft Graphics Component2Windows Update Assistant2Windows User Profile Service2ASP.NET Core & Visual Studio1Microsoft Azure Active Directory Connect1
Every patch

Browse all 132 entries

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

Showing 45 of 45
45 Microsoft vulnerabilities in the August 2021 Patch Tuesday, sortable by severity, CVSS and exploit status.
TitleStatusKB
ImportantCVE-2021-36948Windows Update Medic Service Elevation of Privilege VulnerabilityEoP7.8ExploitedWindows Update5005030 +2
CriticalCVE-2021-36936Windows Print Spooler Remote Code Execution VulnerabilityRCE8.8DisclosedMore likelyWindows Print Spooler Components5005030 +12
ImportantCVE-2021-36958Windows Print Spooler Remote Code Execution VulnerabilityRCE7.8DisclosedMore likelyWindows Print Spooler Components5005565 +12
ImportantCVE-2021-36942Windows LSA Spoofing VulnerabilitySpoofing7.5DisclosedMore likelyWindows NTLM5005030 +10
CriticalCVE-2021-26424Windows TCP/IP Remote Code Execution VulnerabilityRCE9.9More likelyWindows TCP/IP5005030 +12
CriticalCVE-2021-26432Windows Services for NFS ONCRPC XDR Driver Remote Code Execution VulnerabilityRCE9.8More likelyWindows Services for NFS ONCRPC XDR Driver5005030 +8
CriticalCVE-2021-34535Remote Desktop Client Remote Code Execution VulnerabilityRCE8.8More likelyRemote Desktop Client5005030 +10
CriticalCVE-2021-34480Scripting Engine Memory Corruption VulnerabilityRCE6.8More likelyMicrosoft Scripting Engine5005030 +8
ImportantCVE-2021-36947Windows Print Spooler Remote Code Execution VulnerabilityRCE8.8More likelyWindows Print Spooler Components5005030 +12
CriticalCVE-2021-34530Windows Graphics Component Remote Code Execution VulnerabilityRCE7.8—Microsoft Graphics Component5005030 +4
CriticalCVE-2021-34534Windows MSHTML Platform Remote Code Execution VulnerabilityRCE6.8—Windows MSHTML Platform5005030 +4
ImportantCVE-2021-34524Microsoft Dynamics 365 On-Premises Remote Code Execution VulnerabilityRCE8.1—Microsoft Dynamics 3654618795 +1
ImportantCVE-2021-26425Windows Event Tracing Elevation of Privilege VulnerabilityEoP7.8—Windows Event Tracing5005030 +12
ImportantCVE-2021-26431Windows Recovery Environment Agent Elevation of Privilege VulnerabilityEoP7.8—Windows Update Assistant5005033
ImportantCVE-2021-34471Microsoft Defender Elevation of Privilege VulnerabilityEoP7.8—Microsoft Defender—
ImportantCVE-2021-34478Microsoft Office Remote Code Execution VulnerabilityRCE7.8—Microsoft Office—
ImportantCVE-2021-34483Windows Print Spooler Elevation of Privilege VulnerabilityEoP7.8—Windows Print Spooler Components5005030 +12
ImportantCVE-2021-34484Windows User Profile Service Elevation of Privilege VulnerabilityEoP7.8—Windows User Profile Service5005030 +12
ImportantCVE-2021-34486Windows Event Tracing Elevation of Privilege VulnerabilityEoP7.8—Windows Event Tracing5005030 +2
ImportantCVE-2021-34533Windows Graphics Component Font Parsing Remote Code Execution VulnerabilityRCE7.8—Microsoft Graphics Component5005030 +12
ImportantCVE-2021-34536Windows Storage Spaces Controller Elevation of Privilege VulnerabilityEoP7.8—Windows Storage Spaces Controller5005030 +4
ImportantCVE-2021-34537Windows Bluetooth Driver Elevation of Privilege VulnerabilityEoP7.8—Windows Bluetooth Service5005030 +8
ImportantCVE-2021-36927Windows Digital TV Tuner device registration application Elevation of Privilege VulnerabilityEoP7.8—Windows Media5011525 +7
ImportantCVE-2021-36937Windows Media MPEG-4 Video Decoder Remote Code Execution VulnerabilityRCE7.8—Microsoft Windows Codecs Library5005030 +12
ImportantCVE-2021-36941Microsoft Word Remote Code Execution VulnerabilityRCE7.8—Microsoft Office Word—
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 47 KB articles across every endpoint, staging them in rings, verifying installed state and producing the compliance evidence. See patch management →

Archive

Previous Patch Tuesdays

Every month Microsoft has published back to January 2016, each with the same breakdown and the full CVE list.

Older months104 releases, October 2024 – January 2016
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.

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 November 10, 2026.

Microsoft fixed 45 vulnerabilities in August 2021, across Windows, Azure, Developer Tools and Microsoft Dynamics. 7 are rated Critical, 3 were publicly disclosed before the patch shipped, and 1 was already being exploited. Note that Microsoft's release document lists 132 entries in total, but 74 of those are Azure Linux package updates and 13 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 13 Edge entries alongside Microsoft product fixes would inflate the headline number and imply work for your Windows Update rings that does not exist.