Trinetri logo
Updated monthly

Microsoft Patch Tuesday
October 2021

Microsoft's October 2021 Patch Tuesday fixes 75 vulnerabilities across Windows, Microsoft Office and Developer Tools - 3 rated Critical, 3 publicly disclosed before the patch shipped, one already exploited in the wild. Patch CVE-2021-40449 first.

Released October 12, 2021, 10:00 PT1 actively exploited3 publicly disclosed37 KB articles to deploy

October 2021 Patch Tuesday at a glance

75
Microsoft CVEs
excl. Edge & Azure Linux
3
Critical
4% of the release
1
Actively exploited
CVE-2021-40449
3
Publicly disclosed
known before the patch
9.0
Highest CVSS
CVE-2021-26427
37
KB articles
what you actually deploy

Why this number differs from other roundups. Microsoft's October 2021 release document lists 183 entries. 77 are Azure Linux (Mariner) OS package updates and 31 are republished Chromium fixes for Edge - neither is a Microsoft product vulnerability. The 75 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 183 entries actually come from

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

75 Microsoft products77 Azure Linux (Mariner)31 Edge (Chromium)

Severity

Microsoft channel only · 75 CVEs

October 2021 severity breakdown
Critical3
Important71
Moderate0
Low1

Impact type

What an attacker gains if it works

October 2021 impact breakdown
Elevation of Privilege21
Remote Code Execution20
Information Disclosure13
Spoofing9
Security Feature Bypass7
Denial of Service5

Most-affected components

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

Microsoft Office Excel6Microsoft Office SharePoint5Windows Storage Spaces Controller5Microsoft Exchange Server4Microsoft Dynamics3Microsoft Windows Codecs Library3Visual Studio3Windows Common Log File System Driver3Windows Win32K3Microsoft Office Visio2Role: Windows Hyper-V2Windows AppContainer2
Every patch

Browse all 183 entries

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

Showing 75 of 75
75 Microsoft vulnerabilities in the October 2021 Patch Tuesday, sortable by severity, CVSS and exploit status.
TitleStatusKB
ImportantCVE-2021-40449Win32k Elevation of Privilege VulnerabilityEoP7.8ExploitedWindows Win32K5006667 +14
ImportantCVE-2021-41335Windows Kernel Elevation of Privilege VulnerabilityEoP7.8DisclosedWindows Kernel5006667 +10
ImportantCVE-2021-40469Windows DNS Server Remote Code Execution VulnerabilityRCE7.2DisclosedRole: DNS Server5006669 +11
ImportantCVE-2021-41338Windows AppContainer Firewall Rules Security Feature Bypass VulnerabilityBypass5.5DisclosedWindows AppContainer5006667 +6
ImportantCVE-2021-36970Windows Print Spooler Spoofing VulnerabilitySpoofing8.8More likelyWindows Print Spooler Components5006667 +14
ImportantCVE-2021-40487Microsoft SharePoint Server Remote Code Execution VulnerabilityRCE8.1More likelyMicrosoft Office SharePoint5002028 +2
ImportantCVE-2021-41344Microsoft SharePoint Server Remote Code Execution VulnerabilityRCE8.1More likelyMicrosoft Office SharePoint5002028 +2
ImportantCVE-2021-40443Windows Common Log File System Driver Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Common Log File System Driver5006667 +14
ImportantCVE-2021-40450Win32k Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Win32K5006667 +4
ImportantCVE-2021-40466Windows Common Log File System Driver Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Common Log File System Driver5006667 +14
ImportantCVE-2021-40467Windows Common Log File System Driver Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Common Log File System Driver5006667 +14
ImportantCVE-2021-40470DirectX Graphics Kernel Elevation of Privilege VulnerabilityEoP7.8More likelyWindows DirectX5006667 +6
ImportantCVE-2021-41357Win32k Elevation of Privilege VulnerabilityEoP7.8More likelyWindows Win32K5006670 +2
CriticalCVE-2021-38672Windows Hyper-V Remote Code Execution VulnerabilityRCE8.0—Role: Windows Hyper-V5006674 +1
CriticalCVE-2021-40461Windows Hyper-V Remote Code Execution VulnerabilityRCE8.0—Role: Windows Hyper-V5006667 +4
CriticalCVE-2021-40486Microsoft Word Remote Code Execution VulnerabilityRCE7.8—Microsoft Office Word5001924 +7
ImportantCVE-2021-26427Microsoft Exchange Server Remote Code Execution VulnerabilityRCE9.0—Microsoft Exchange Server5007011 +1
ImportantCVE-2021-40464Windows Nearby Sharing Elevation of Privilege VulnerabilityEoP8.0—Windows Nearby Sharing5006667 +4
ImportantCVE-2021-41348Microsoft Exchange Server Elevation of Privilege VulnerabilityEoP8.0—Microsoft Exchange Server5007012
ImportantCVE-2021-26441Storage Spaces Controller Elevation of Privilege VulnerabilityEoP7.8—Windows Storage Spaces Controller5006667 +10
ImportantCVE-2021-40462Windows Media Foundation Dolby Digital Atmos Decoders Remote Code Execution VulnerabilityRCE7.8—Microsoft Windows Codecs Library5006667 +4
ImportantCVE-2021-40465Windows Text Shaping Remote Code Execution VulnerabilityRCE7.8—Windows Text Shaping5006667 +14
ImportantCVE-2021-40471Microsoft Excel Remote Code Execution VulnerabilityRCE7.8—Microsoft Office Excel5001982 +1
ImportantCVE-2021-40473Microsoft Excel Remote Code Execution VulnerabilityRCE7.8—Microsoft Office Excel5001982 +1
ImportantCVE-2021-40474Microsoft Excel Remote Code Execution VulnerabilityRCE7.8—Microsoft Office Excel5002027 +3
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 37 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 75 vulnerabilities in October 2021, across Windows, Microsoft Office, Developer Tools and Server Software. 3 are rated Critical, 3 were publicly disclosed before the patch shipped, and 1 was already being exploited. Note that Microsoft's release document lists 183 entries in total, but 77 of those are Azure Linux package updates and 31 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 31 Edge entries alongside Microsoft product fixes would inflate the headline number and imply work for your Windows Update rings that does not exist.