Microsoft CEO Satya Nadella warns that fixing bugs discovered using AI could increase IT instability, as the company releases off-schedule updates every month since July. Available estimates show a strong increase in vulnerabilities addressed, without a proportional increase in those actively exploited.
Urgent and sometimes incomplete fixes
For Office, Microsoft recently delivered fixes on Windows while the same bugs also affected the Mac versions. Apple users were advised to follow the company’s upcoming communications for their own update. The existence of the flaws therefore became public before these users had the expected fix. Operation during this interval remained possible.
Exceptional publications often arrive within a few days of an initial delivery. Designated by the acronym OOB, for updates released outside of the schedule, they respond to problems deemed important enough not to wait, frequently linked to security. They can complicate the work of administrators already busy with planned deployments. On the testing side, a large volume also risks leading to accelerated or incomplete controls, particularly on possible regressions.
At the DealBook Summit this week, Satya Nadella used the example of a patch for a critical banking system: it once could have benefited from a week of testing. An already exploited flaw can now require, according to him, an immediate deployment as soon as the correction becomes available. The leader associates this emergency with future instability.
Various regulatory frameworks require companies to verify the security of patches for their own systems.
More than 1,400 CVEs processed in October
Since January 2021, Microsoft has reportedly fixed around 10,319 CVEs, including 5,383 for 2026, or more than half. Of these, 5,128 have been processed since April. The estimated total for 2025 was 1,180.
These numbers require caution: counting methods differ, particularly for Edge, which depends on corrections from the Chromium project. Other analysts thus arrive at higher or lower results. In this estimated series, the first quarter of 2026 represents 255 CVEs, then April 163, May 132 and June 209. The figure increases to 575 in July and would have crossed 1,400 in October.
The majority of bugs in this influx are believed to come from new researchers, rather than the usual contributors to product security. Discoveries would appear simultaneously in several people without apparent collaboration. They would, for the most part, be relatively minor. The number of vulnerabilities actually exploited would not increase in the same proportions as the total.
The evening letterFree · 7 p.m.
Do you want the best AI tools before the rest?
We test and decipher the new AI tools every evening, in 5 minutes. Free.
Included upon registration: our selection of the best AI guides & comparisons.
Choose your pace
Free · No spam · Unsubscribe in 1 click
The monthly CVSS severity average, which tended to be around 7.8 out of 10 before 2026, would have fallen to around 7.4 in September 2026.
MAPP coordinates the preparation of patches
At Microsoft, patch coordination is the responsibility of the Microsoft Active Protections Program, MAPP, led by the Microsoft Security Response Center, or MSRC. The program reached 18 years this year. Its partners receive information on bugs in advance before Patch Tuesday, the regular delivery organized every second Tuesday of the month. MAPP also coordinates the preparation of this publication internally.
A report leads to an investigation and then the preparation of a correction. When multiple versions of software remain supported, different teams may need to review the report, reproduce the defect, design the response, and test it. Controls also cover undesirable effects and the risk that a patch indirectly reveals a similar flaw elsewhere. We must then prepare for its large-scale distribution.
The MAPP ensures with the teams that the corrections are ready and determines the information that can be transmitted without risk to partners and the public. The MSRC participates, more broadly, in the processing of reports from external researchers. To prioritize the most serious bugs, it has the Software and Services Incident Response Plan, or SSIRP, which dates back to 2004. Other companies and communities supporting Linux have their own coordination mechanisms.
Some partners have already disclosed details received in advance. In 2025, attacks targeting SharePoint raised suspicions of a leak from the program. Microsoft then removed early access for Chinese companies.
The limits of automation and recent breakdowns
Part of the processing could be automated. Many steps, however, rely on judgmental decisions that current AI systems cannot reliably handle. MAPP is a small human team.
Some researchers transmit incomplete elements, sometimes a simple report of a crash accompanied by a request for payment. They can also make their discovery public if they consider the reaction insufficient.
An update that disrupted Teams, Outlook, SharePoint and other software wasn’t a direct attack using AI; neither did the FAA shutdown. At the New York Times DealBook Summit on Wednesday, Satya Nadella attributed the previous week’s Microsoft 365 outage to a latent bug, not directly related to AI.
That same Wednesday, in an interview when asked about outages at United, Schwab, Chase and other organizations, the executive distinguished the discovery of defects from the application of their fixes. He said AI helps find bugs and fix them, but deploying them can produce instability. In particular, he pointed to the accumulation of patches on old infrastructures as a factor of reduced stability.

