Microsoft’s patches triple in three months, IT must prioritize by exposure rather than severity

Microsoft’s monthly patch updates have surged more than threefold over the past three months, coinciding with the company’s increasing use of AI in vulnerability detection. The October release addresses more vulnerabilities than any previous update, including an actively exploited flaw in Windows. The sheer volume of patches now exceeds what any single team can deploy at once, making prioritization by risk exposure the only viable strategy for IT departments.

Since the summer, the pace of Microsoft’s updates has escalated dramatically. The July batch set a record with 622 vulnerabilities, followed by CrowdStrike’s count of 415 in August and an alarming 972 in September. On October 13, Microsoft rolled out its monthly updates, and CrowdStrike identified a staggering 1,413 vulnerabilities in this release, including 75 deemed critical.

Among these, only one vulnerability had been exploited prior to its fix. The CVE-2026-96951 flaw bypasses Windows’ “Mark of the Web” protection mechanism, which indicates when a file comes from the internet, necessitating user action for exploitation. Additionally, two flaws were made public before the patch: CVE-2026-108398 in .NET Framework, which circumvents WDAC application controls, and CVE-2026-92707 in the MessagePack-CSharp library.

### Prioritizing Exposure: Preview Panes, Network, and Directory Vulnerabilities

CrowdStrike’s assessment isolates vulnerabilities that require no action from victims. There are 23 that can be triggered by the Outlook or Office preview pane, and 15 enable remote code execution without authentication, such as CVE-2026-96934 affecting Windows DHCP servers, rated at 9.8. The CVE-2026-70571 vulnerability in Exchange Server can be activated simply by an incoming email, although its exploitation is considered complex.

Another significant portion of these flaws is concentrated in Office applications. Among the 20 remote code execution fixes for Office, Excel accounts for 11 and PowerPoint for five. Notably, CVE-2026-88178 in PowerPoint hits 9.8 in severity, as it can be exploited without authentication via the Office Online service. Outlook has five vulnerabilities rated 9.8, including CVE-2026-70291 and CVE-2026-88156, which can be triggered just by previewing a message. The French cybersecurity agency CERT-FR highlighted these vulnerabilities in five advisories on October 14.

Windows servers are also not exempt from these vulnerabilities. CVE-2026-70229 allows for remote code execution on Active Directory domain controllers without authentication, although it has a high complexity rating. Two Hyper-V vulnerabilities, CVE-2026-102214 and CVE-2026-105733, enable a virtual machine to escape to its host, affecting servers whose compromise could jeopardize the entire information system.

### Record Volume Amid Declining Risk Levels

The increase in the volume of vulnerabilities markedly outpaces the rise in risk. According to CrowdStrike, the number of critical vulnerabilities dropped from 113 in September to 75 in October, while 977 entries pertain to extended security updates for older Windows versions. Elevation of privilege vulnerabilities make up 48% of the total, with remote code executions at 22% and information disclosures at 18%.

In an effort to improve its vulnerability discovery, Microsoft has revamped its approach, as noted by Taesoo Kim, vice president of agent security, on October 7. The company’s FORGE lab has helped identify vulnerabilities that received 140 CVE IDs from May to September, with 52 identified in the September batch. However, this accounts for merely 5% of September’s total vulnerabilities, suggesting that while AI-driven research plays a role, it does not fully explain the spike.

The contribution from this lab is steadily increasing, with the number of identified vulnerabilities rising from 16 in May to 10 in June, 27 in July, 35 in August, and 52 in September. Microsoft clarifies that these figures reflect publication dates, not discovery dates.

### Shorter Exploitation Windows Exceed Testing Cycles

The pressure on IT teams is mounting as the time available for remediation decreases. For instance, a SharePoint vulnerability was exploited within hours of a proof-of-concept release—only six days after the patch was issued. Similarly, an Adobe ColdFusion flaw was exploited three weeks post-patch. Lists of known exploits, such as those published by CISA, the U.S. cybersecurity agency, serve as an essential triage tool for teams unable to test every vulnerability.

This filtering process is not always adequate for flaws that are disclosed before a patch is available. The vulnerabilities in .NET Framework and MessagePack-CSharp were not exploited as of October 13, but their public descriptions significantly shorten an attacker’s work. Consequently, passing these patches to development teams for internal project updates remains critical.

### Prioritization by Exposure: A Strategy Over Severity Ratings

The key lesson for patch management teams from the October update lies less in the sheer volume of vulnerabilities and more in the methodology required to address them. Implementing a comprehensive patch across a few days demands testing resources that many organizations lack at such scales. Moreover, the severity rating does not accurately reflect urgency, as the only actively exploited flaw is not classified as critical.

Thus, a prioritization strategy based on actual exposure—considering exploited vulnerabilities, lack of authentication, clickless triggers, and affecting directory servers—remains the most prudent approach.

This discipline will be essential beyond October, particularly if automated vulnerability research continues to rise. Microsoft’s recent announcement of ongoing validation for flaws identified by its models underscores this trend, but it also places additional expectations on clients, forcing them to apply more patches within the same timeframe. IT leaders lacking a formal prioritization strategy will find compelling reasons to establish one based on this update.

Scroll to Top