Trinetri logo
Updated monthly

Microsoft Patch Tuesday
November 2021

Microsoft's November 2021 Patch Tuesday fixes 57 vulnerabilities across Windows, Azure and Developer Tools - 6 rated Critical, 5 publicly disclosed before the patch shipped, 2 already exploited in the wild. Patch CVE-2021-42321 first.

Released November 9, 2021, 10:00 PT2 actively exploited5 publicly disclosed29 KB articles to deploy

November 2021 Patch Tuesday at a glance

57
Microsoft CVEs
excl. Edge & Azure Linux
6
Critical
11% of the release
2
Actively exploited
CVE-2021-42321
5
Publicly disclosed
known before the patch
9.0
Highest CVSS
CVE-2021-26443
29
KB articles
what you actually deploy

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

Priority order

Patch these first

Ranked by exploitation reality, not score alone. This month's exploited flaw is rated Important - a severity-sorted list would bury it.

The numbers

What’s in this release

Where the 120 entries actually come from

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

57 Microsoft products41 Azure Linux (Mariner)22 Edge (Chromium)

Severity

Microsoft channel only · 57 CVEs

November 2021 severity breakdown
Critical6
Important51
Moderate0
Low0

Impact type

What an attacker gains if it works

November 2021 impact breakdown
Elevation of Privilege22
Remote Code Execution15
Information Disclosure11
Spoofing3
Denial of Service3
Security Feature Bypass2
Tampering1

Most-affected components

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

Azure Real Time Operating System6Azure Sphere4Windows Active Directory4Windows NTFS4Windows RDP4Microsoft Exchange Server33D Viewer2Azure2Microsoft Office Excel2Role: Windows Hyper-V2Visual Studio2Windows Update Assistant2
Every patch

Browse all 120 entries

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

Showing 57 of 57
57 Microsoft vulnerabilities in the November 2021 Patch Tuesday, sortable by severity, CVSS and exploit status.
TitleStatusKB
ImportantCVE-2021-42321Microsoft Exchange Server Remote Code Execution VulnerabilityRCE8.8ExploitedMicrosoft Exchange Server5007409
ImportantCVE-2021-42292Microsoft Excel Security Feature Bypass VulnerabilityBypass7.8ExploitedMicrosoft Office Excel4486670 +3
ImportantCVE-2021-432083D Viewer Remote Code Execution VulnerabilityRCE7.8Disclosed3D Viewer—
ImportantCVE-2021-432093D Viewer Remote Code Execution VulnerabilityRCE7.8Disclosed3D Viewer—
ImportantCVE-2021-43211Windows 10 Update Assistant Elevation of Privilege VulnerabilityEoP5.5DisclosedWindows Update Assistant—
ImportantCVE-2021-38631Windows Remote Desktop Protocol (RDP) Information Disclosure VulnerabilityInfo Disc.4.4DisclosedWindows RDP5007186 +14
ImportantCVE-2021-41371Windows Remote Desktop Protocol (RDP) Information Disclosure VulnerabilityInfo Disc.4.4DisclosedWindows RDP5007186 +14
CriticalCVE-2021-38666Remote Desktop Client Remote Code Execution VulnerabilityRCE8.8More likelyWindows RDP5007186 +14
CriticalCVE-2021-42298Microsoft Defender Remote Code Execution VulnerabilityRCE7.8More likelyWindows Defender—
ImportantCVE-2021-41356Windows Denial of Service VulnerabilityDoS7.5More likelyMicrosoft Windows5007186 +6
CriticalCVE-2021-26443Microsoft Virtual Machine Bus (VMBus) Remote Code Execution VulnerabilityRCE9.0—Windows Virtual Machine Bus5007186 +4
CriticalCVE-2021-42316Microsoft Dynamics 365 On-Premises Remote Code Execution VulnerabilityRCE8.8—Microsoft Dynamics5008478 +1
CriticalCVE-2021-42279Chakra Scripting Engine Memory Corruption VulnerabilityRCE4.2—Windows Scripting5007186 +6
CriticalCVE-2021-3711OpenSSL: CVE-2021-3711 SM2 Decryption Buffer OverflowRCE-—Visual Studio—
ImportantCVE-2021-42275Microsoft COM for Windows Remote Code Execution VulnerabilityRCE8.8—Windows COM5007186 +13
ImportantCVE-2021-42283NTFS Elevation of Privilege VulnerabilityEoP8.8—Windows NTFS5007186 +14
ImportantCVE-2021-42306Azure Active Directory Information Disclosure VulnerabilityInfo Disc.8.1—Azure—
ImportantCVE-2021-36957Windows Desktop Bridge Elevation of Privilege VulnerabilityEoP7.8—Windows Desktop Bridge5007186 +5
ImportantCVE-2021-40442Microsoft Excel Remote Code Execution VulnerabilityRCE7.8—Microsoft Office Excel5002053 +4
ImportantCVE-2021-41366Credential Security Support Provider Protocol (CredSSP) Elevation of Privilege VulnerabilityEoP7.8—Windows Cred SSProvider Protocol5007186 +10
ImportantCVE-2021-41367NTFS Elevation of Privilege VulnerabilityEoP7.8—Windows NTFS5007186 +14
ImportantCVE-2021-41370NTFS Elevation of Privilege VulnerabilityEoP7.8—Windows NTFS5007186 +14
ImportantCVE-2021-41377Windows Fast FAT File System Driver Elevation of Privilege VulnerabilityEoP7.8—Windows Fast FAT Driver5007186 +14
ImportantCVE-2021-41378Windows NTFS Remote Code Execution VulnerabilityRCE7.8—Windows NTFS5007186 +4
ImportantCVE-2021-42276Microsoft Windows Media Foundation Remote Code Execution VulnerabilityRCE7.8—Microsoft Windows Codecs Library5007186 +6
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 29 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 57 vulnerabilities in November 2021, across Windows, Azure, Developer Tools and Microsoft Office. 6 are rated Critical, 5 were publicly disclosed before the patch shipped, and 2 were already being exploited. Note that Microsoft's release document lists 120 entries in total, but 41 of those are Azure Linux package updates and 22 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 22 Edge entries alongside Microsoft product fixes would inflate the headline number and imply work for your Windows Update rings that does not exist.