Uptime Report Research · Patch Data

Patch Tuesday Statistics 2026: Microsoft Patched Three Times More Flaws, Not Three Times More Zero-Days

Patch Tuesday statistics are usually reported one month at a time. We pulled every monthly release from Microsoft’s Security Update Guide API since January 2021 and counted the vulnerabilities Microsoft itself assigned, leaving out the Linux and Chromium entries that the same feed now carries. The 2026 numbers break every prior year, but the count of flaws exploited before a fix did not move.

2,859Microsoft CVEs, Jan to Sep 2026
896same months of 2025
19 vs 20exploited zero-days, 2026 vs 2025 (same months)

Every Patch Tuesday since 2021

2021 to 2025 2026 one exploited zero-day

020040060080010002021-Jan: 81 CVEs, 1 exploited2021-Feb: 56 CVEs, 1 exploited2021-Mar: 89 CVEs, 7 exploited2021-Apr: 108 CVEs, 1 exploited2021-May: 52 CVEs, 0 exploited2021-Jun: 49 CVEs, 6 exploited2021-Jul: 119 CVEs, 4 exploited2021-Aug: 45 CVEs, 1 exploited2021-Sep: 60 CVEs, 1 exploited2021-Oct: 72 CVEs, 1 exploited2021-Nov: 56 CVEs, 2 exploited2021-Dec: 68 CVEs, 1 exploited2022-Jan: 96 CVEs, 2 exploited2022-Feb: 48 CVEs, 0 exploited2022-Mar: 70 CVEs, 0 exploited2022-Apr: 117 CVEs, 1 exploited2022-May: 75 CVEs, 2 exploited2022-Jun: 50 CVEs, 0 exploited2022-Jul: 82 CVEs, 1 exploited2022-Aug: 120 CVEs, 1 exploited2022-Sep: 65 CVEs, 3 exploited2022-Oct: 84 CVEs, 1 exploited2022-Nov: 62 CVEs, 5 exploited2022-Dec: 48 CVEs, 1 exploited2023-Jan: 98 CVEs, 1 exploited2023-Feb: 75 CVEs, 3 exploited2023-Mar: 74 CVEs, 2 exploited2023-Apr: 98 CVEs, 1 exploited2023-May: 38 CVEs, 2 exploited2023-Jun: 75 CVEs, 0 exploited2023-Jul: 130 CVEs, 5 exploited2023-Aug: 74 CVEs, 1 exploited2023-Sep: 59 CVEs, 2 exploited2023-Oct: 103 CVEs, 2 exploited2023-Nov: 58 CVEs, 3 exploited2023-Dec: 34 CVEs, 0 exploited2024-Jan: 48 CVEs, 0 exploited2024-Feb: 72 CVEs, 4 exploited2024-Mar: 61 CVEs, 0 exploited2024-Apr: 147 CVEs, 1 exploited2024-May: 60 CVEs, 2 exploited2024-Jun: 50 CVEs, 0 exploited2024-Jul: 142 CVEs, 2 exploited2024-Aug: 89 CVEs, 6 exploited2024-Sep: 82 CVEs, 5 exploited2024-Oct: 121 CVEs, 2 exploited2024-Nov: 94 CVEs, 3 exploited2024-Dec: 73 CVEs, 1 exploited2025-Jan: 162 CVEs, 3 exploited2025-Feb: 58 CVEs, 3 exploited2025-Mar: 62 CVEs, 6 exploited2025-Apr: 127 CVEs, 1 exploited2025-May: 78 CVEs, 5 exploited2025-Jun: 69 CVEs, 1 exploited2025-Jul: 135 CVEs, 1 exploited2025-Aug: 114 CVEs, 0 exploited2025-Sep: 91 CVEs, 0 exploited2025-Oct: 179 CVEs, 2 exploited2025-Nov: 71 CVEs, 1 exploited2025-Dec: 63 CVEs, 1 exploited2026-Jan: 123 CVEs, 2 exploited2026-Feb: 59 CVEs, 6 exploited2026-Mar: 95 CVEs, 0 exploited2026-Apr: 179 CVEs, 2 exploited2026-May: 153 CVEs, 3 exploited2026-Jun: 216 CVEs, 0 exploited2026-Jul: 596 CVEs, 3 exploited2026-Aug: 445 CVEs, 1 exploited2026-Sep: 993 CVEs, 2 exploited202120222023202420252026

Microsoft-assigned CVEs per monthly release, excluding Edge (Chromium-based), Azure Linux, and other third-party entries. Red dots above each bar stack one per CVE marked “Exploited: Yes”.

From 2021 to 2025, Microsoft fixed between 855 and 1,209 of its own CVEs a year. In 2026, the total through Sep is 2,859, up 219% on the same months of 2025, and 2,034 of those arrived in July, August, and September alone. The largest single release was 2026-Sep, with 993.

Where the surge came from

The third-quarter jump is spread across core products rather than one component. Product families with the most CVEs in July to September 2026, against the same quarter of 2025:

Product family Q3 2026 Q3 2025
Microsoft Office Excel 95 15
Microsoft Office 72 12
SQL Server 68 10
Microsoft Office Word 67 8
Microsoft Office SharePoint 64 8
Windows Biometric Service 64 0
Windows NTFS 61 3
Windows DHCP Server 57 0

Zero-days did not triple

19 CVEs fixed in 2026 are flagged as exploited in the wild, compared with 20 in the same months of 2025. Most of the growth is in vulnerabilities found and fixed before attackers used them. For patch prioritization that is the key ratio: in 2026, roughly 1 in 150 Microsoft CVEs was exploited before its fix, against 1 in 45 a year earlier.

  • CVE-2026-20805 Desktop Window Manager 2026-Jan
  • CVE-2026-21509 Microsoft Office 2026-Jan
  • CVE-2026-21519 Desktop Window Manager 2026-Feb
  • CVE-2026-21533 Windows Remote Desktop 2026-Feb
  • CVE-2026-21513 MSHTML Framework 2026-Feb
  • CVE-2026-21510 Windows Shell 2026-Feb
  • CVE-2026-21514 Microsoft Office Word 2026-Feb
  • CVE-2026-21525 Windows Remote Access Connection Manager 2026-Feb
  • CVE-2026-32201 Microsoft Office SharePoint 2026-Apr
  • CVE-2026-32202 Windows Shell 2026-Apr
  • CVE-2026-41091 Microsoft Defender 2026-May
  • CVE-2026-42897 Microsoft Exchange Server 2026-May
  • CVE-2026-45498 Microsoft Defender 2026-May
  • CVE-2026-56155 Active Directory Federation Services (AD FS) 2026-Jul
  • CVE-2026-56164 Microsoft Office SharePoint 2026-Jul
  • CVE-2026-58644 Microsoft Office SharePoint 2026-Jul
  • CVE-2026-68820 Windows Ancillary Function Driver for WinSock 2026-Aug
  • CVE-2026-81963 Windows Update Stack 2026-Sep
  • CVE-2026-85880 Windows ALPC 2026-Sep

Year by year

Year CVEs Exploited Critical Remote code execution Elevation of privilege Cloud, no action
2021 855 26 11.7% 37% 30% 0
2022 917 17 9.4% 33% 41% 0
2023 916 22 9.3% 36% 26% 0
2024 1,039 26 7.0% 39% 30% 23
2025 1,209 24 13.0% 30% 40% 68
2026* 2,859 19 15.8% 24% 45% 174

*2026 is January to Sep. Critical is Microsoft’s maximum severity rating for the CVE. Impact is the most frequent impact rating across affected products.

What this means for MSPs

A tripling of monthly patch volume strains testing and deployment windows, but the exploited share fell. Treat the exploited and publicly disclosed CVEs as same-week deployments, follow Critical remote code execution flaws in internet-facing services next, and let the remaining volume flow through normal rings. Cloud-service CVEs marked as requiring no customer action can be excluded from patch reporting to clients.

Frequently asked questions

How many vulnerabilities did Microsoft patch in 2026?

From January to Sep 2026, Microsoft’s security update guide lists 2,859 CVEs assigned by Microsoft itself, compared with 896 in the same months of 2025. That already exceeds every full year in our series; the previous high was 1,209 in 2025.

How many zero-days has Microsoft patched in 2026?

19 of the 2026 CVEs are currently marked as exploited in the wild, compared with 20 in January to Sep 2025. The number of exploited flaws did not rise with the total.

Which Microsoft products have the most vulnerabilities in 2026?

In July to September 2026, the product families with the most CVEs were Microsoft Office Excel (95), Microsoft Office (72), and SQL Server (68).

What was the biggest Patch Tuesday?

2026-Sep, with 993 Microsoft-assigned CVEs in our data.

What are cloud CVEs with no customer action?

Since 2024-Jun, Microsoft has also published CVEs for vulnerabilities it fixed in its own cloud services, marked as requiring no customer action. There were 174 in 2026 through Sep. They count toward totals but need no patching by MSPs or clients.

Download the data. microsoft-patch-tuesday-cves-2021-2026.csv (CSV). Licensed under CC BY 4.0: free to reuse with attribution to The Uptime Report.

Methodology

Source. Microsoft Security Response Center, Security Update Guide CVRF API v3.0, one document per monthly release, retrieved October 2026. The 2026 October release was not yet published at retrieval.

Filters. Kept CVEs whose assigning CNA note is Microsoft (or, in older documents with no CNA note, entries not tagged Azure Linux). Excluded security advisories (ADV), Microsoft Edge (Chromium-based) entries, and Azure Linux (Mariner) entries, which cover third-party open source packages. With these filters, monthly counts match Microsoft’s published totals for spot-checked months (for example, 48 in January 2024 and 142 in July 2024).

Coverage. The series starts in January 2021 because several earlier monthly documents in the API (including October 2017, September 2018, and March, April, and October 2020) now contain only backfilled Azure Linux entries.

Limitations. Exploited and severity flags reflect Microsoft’s current ratings, which can be revised after release. One CVE can affect several products; product family is the first tag listed.

Not advice. This is an analysis of public vulnerability data, not a patching recommendation for any environment.

Cite as:The Uptime Report. "Patch Tuesday Statistics 2026: Microsoft Patched Three Times More Flaws, Not Three Times More Zero-Days." October 2026. https://theuptimereport.com/patch-tuesday-statistics-2026/

References

  1. Microsoft Security Response Center, Security Update Guide. Accessed October 2026.
  2. MSRC CVRF API v3.0, updates index. Accessed October 2026.

Research library

More original data reports from The Uptime Report. Every report includes its methodology and a free CSV download. Browse all research

Threats and breaches

Infrastructure and uptime

Regulation and disclosure

Workforce and pay

MSP market and spending

Comments

10 responses to “Patch Tuesday Statistics 2026: Microsoft Patched Three Times More Flaws, Not Three Times More Zero-Days”

  1. […] Patch Tuesday Statistics 2026Every Microsoft CVE since 2021 […]

  2. […] Patch Tuesday Statistics 2026Every Microsoft CVE since 2021 […]

  3. […] Patch Tuesday Statistics 2026Every Microsoft CVE since 2021 […]

  4. […] help desk, backup and disaster recovery, security, patching, and technology guidance, delivered proactively for a monthly […]

  5. […] covers monitoring, configuration, patching, and capacity […]

  6. […] might run the after-hours help desk, supply security tools the team cannot staff, or take on patching and monitoring while the internal staff focus on projects and […]

  7. […] were never patched, which is why asset inventory and legacy-system coverage matter as much as fast patching of new […]

  8. […] against 481 in all of 2025. That matches the jump in total Microsoft fixes this year shown in our Patch Tuesday statistics for 2026, and the wider rise in published vulnerabilities tracked in our CVE statistics for 2026. Exploited […]

  9. […] Vulnerabilities Microsoft assigned and fixed in the first nine months of 2026, up 219% from 896 in the same months of 2025, in our count of every Patch Tuesday release. […]

  10. […] so a fully migrated fleet can still be out of date. The same Patch Tuesday cadence we track in our Patch Tuesday statistics stops reaching any version past its […]

Leave a Reply

Your email address will not be published. Required fields are marked *