Microsoft's own numbers, published November 2, put the median time to patch a vulnerability on Windows Servers at "more than a month". In Senserva's conversations with Microsoft administrators, a month is often the better case. Change windows, testing, servers without a clear owner, and devices that never appear in the Windows patch report all push it longer.
Attackers are moving the other way. Microsoft cites CISA data for 2026 through September: the time from a CVE's publication to its addition to the Known Exploited Vulnerabilities catalog is down to a mean of 20 days, "with a median of only 3 days since publication."
A month to patch against days to exploit is the problem. Fixing it, and the other ways patching goes wrong, is what Senserva is focused on. This post starts with Microsoft's numbers, then covers two places this month where the gap gets wider: nine Windows CVEs that Microsoft now says also affect Office for Mac and Office for Android, which a Windows patch report will not show, and the Extended Security Updates programs that ended in October, after which some servers get no patch at all. It ends with what we are doing about it.
We track and share this information; we are not the source of it. Every fact below links to the Microsoft page it comes from. The short version went out as the November 3 Senserva Watch alert.
A month to patch, days to exploit
On November 2, Microsoft Security Research published an analysis of the CVEs published through September 2026. On patch speed, Microsoft cites its Security Exposure Management data from 2026: "the median vulnerability is patched in about two weeks on Windows workstations but in more than a month on Windows Servers." On exploitation speed, Microsoft cites CISA for the mean time from CVE publication to the Known Exploited Vulnerabilities catalog, which "fell from 89 days in 2024 to 57 days in 2025", and adds that "2026 data up to September already have that number dropping to 20 days, with a median of only 3 days since publication."
Microsoft's guidance: "Patching remains essential, but remediation can take weeks or months on critical systems, and some legacy or unsupported systems cannot be patched. Defenders therefore need to concentrate protection where it can have the greatest impact, considering both the likelihood of exploitation and the potential blast radius of a successful attack."
What attackers go after
The same analysis shows which flaws get used. Microsoft writes that "approximately 383,000 software vulnerabilities had been disclosed across platforms and technologies, yet only about 2,000 CVEs (roughly 0.5%) have been linked to real-world exploitation." Takeover vulnerabilities, "like remote code execution, authentication bypass and local privilege escalation", "account for 78% of real-world exploited vulnerabilities". Its comparison with all published CVEs:
"Server-side RCE rises from 20% of published CVEs to 37% of exploited CVEs, local privilege escalation from 11% to 18%, and client-side RCE from 4% to 13%. By comparison, XSS falls from 15% to 4% and denial of service from 16% to 7%."
Microsoft also reports that operating system flaws rise "from 23% of the overall CVE population to 41% of exploited vulnerabilities", and cautions that "a vulnerability's stated classification does not always reflect what an attacker can reliably achieve in practice."
Servers are where the two halves meet: they are the slowest to patch, and server-side remote code execution is 37% of what is exploited. A Windows Server that has left support gets no patch at all unless it is covered by Extended Security Updates, covered in the third section below.
Where the gap gets wider: Office for Mac and Android
A month to patch assumes the update shows up in your patch report. On October 28, Microsoft revised nine Windows vulnerabilities it first published in July, August and September. Each revision says Microsoft "Added supported editions of Microsoft Office to the Security Updates table because they are affected by this vulnerability" and that it "recommends that customers running any of these editions of Office install the latest security updates to be fully protected from this vulnerability."
The editions added in Microsoft's Security Update Guide are Microsoft Office 365 for Mac, Microsoft Office LTSC for Mac 2021 and 2024, and Microsoft Office for Android. Office for Windows is not among them. For these editions, Microsoft points to the Office release notes for the fix, not to a Windows update, so a Windows patch report will not show them.
Microsoft rates two of the nine Critical, both Windows Imaging Component remote code execution at CVSS 8.8:
- CVE-2026-69499 (September): Office for Mac and Office for Android
- CVE-2026-73013 (September): Office for Android
The other seven are rated Important. They include CVE-2026-69576 (Graphic Fonts Elevation of Privilege) and CVE-2026-62877 (Windows Win32k Elevation of Privilege), both CVSS 7.8, and information disclosure in GDI (CVE-2026-77491), Win32k (CVE-2026-69609) and three more from July and August.
Microsoft's tables give the fixed builds: Office for Mac 16.112.26090911 and Office for Android 16.0.20430.20000. Microsoft's Office for Mac release notes date Version 16.112.4 (Build 26090911) to September 10, 2026, and list Version 16.114.3 on October 27. So a Mac on any build from September 10 or later already has the fix; the work is finding the Macs and Android devices that have not updated.
Microsoft lists none of the nine as exploited or publicly disclosed, and none is in CISA's Known Exploited Vulnerabilities catalog. The reference for the Office editions is Microsoft's Security Update Guide; our CVE pages do not show them yet, which is one of the things we are fixing (see the last section).
Where there is no patch at all: Extended Security Updates
Extended Security Updates (ESU) are Microsoft's paid program for receiving security fixes after a product's support has ended. In Microsoft's words from its lifecycle FAQ, ESU "includes Critical* and/or Important* security updates up to three years after the product's End of Extended Support date. The ESU program does not extend the product's lifecycle and does not provide technical support beyond the original support timeline." No new features and no non-security fixes come with it.
That makes ESU the answer to the "legacy or unsupported systems" in Microsoft's guidance above, for as long as it lasts. October 2026 ended two ESU programs, and the next end of support is ten weeks away.
Ended in October
- Windows Server 2012 and 2012 R2. Microsoft's Azure Arc ESU page says: "The three-year ESU period ends on October 13, 2026, and the October 13, 2026 security update is the final update provided through ESUs." A Windows Server 2012 machine still running today receives no further security updates.
- Exchange Server 2016 and 2019. The Exchange team updated its ESU announcement on October 13: "We have released the final set of updates under the Exchange 2016/2019 ESU program. There will be no more updates released for Exchange 2016/2019." It adds: "This does not mean that those versions are not vulnerable to future security issues." Future updates go to Exchange Server Subscription Edition only.
Still running
- Windows 10 for organizations. Support ended October 14, 2025. Per Microsoft's ESU page for Windows 10, commercial ESU is sold through volume licensing "at $61 USD per device for Year One" and "The price doubles every consecutive year, for a maximum of three years." Year One ended October 13, 2026, and Microsoft's lifecycle FAQ lists Year Two ending October 12, 2027. ESU is cumulative: "If you decide to purchase the program in Year Two, you have to pay for Year One too, as ESUs are cumulative." Microsoft also says "ESU is available at no additional cost for Windows 10 virtual machines" in services including Windows 365, Azure Virtual Desktop and Azure virtual machines.
- Windows 10 at home. Microsoft extended the consumer program on June 25, 2026. Its consumer ESU page says: "You can enroll in ESU any time until the program ends on October 12, 2027." The consumer program does not cover domain-joined, Entra-joined or MDM-enrolled devices.
- SQL Server 2014 and 2016. Both are past extended support and in their ESU years, per Microsoft's lifecycle pages for SQL Server 2014 and SQL Server 2016. SQL Server ESU is narrower than Windows ESU: Microsoft says it "makes ESUs available if needed once a security vulnerability is discovered and rated as Critical by the Microsoft Security Response Center (MSRC)."
Next: Windows Server 2016 on January 12, 2027
Microsoft's Azure Arc ESU page says: "Windows Server 2016 reaches end of support on January 12, 2027. Extended Security Updates for Windows Server 2016 provide Critical and Important security updates for up to three years, through 2030." ESU is for the Standard and Datacenter editions, and "You can configure Windows Server 2016 ESUs in the Azure portal starting August 3, 2026. Billing for Windows Server 2016 ESUs enabled by Azure Arc begins January 13, 2027."
Read that next to Microsoft's patch-speed figures: servers already take more than a month to patch at the median, and after the January 12 update, a Windows Server 2016 machine without ESU receives no more security updates. If you have 2016 servers you cannot upgrade by then, the ESU decision belongs in this quarter's plan. Microsoft's lifecycle page for Windows Server 2016 has the dates, and our end-of-life tracker lists them with the other Microsoft products.
What Senserva is doing about it
More than a month is the median in Microsoft's own data. The items above are the kind that make it longer: a Windows CVE that now affects Office for Mac, an ESU program that quietly ended, a server that leaves support in ten weeks. None of them arrive as a new KB on Patch Tuesday. Senserva is focused on closing that gap: finding what needs patching, including what a normal patch report misses, and showing when it is done.
- Every Microsoft security update has its own page, free to read. Each KB page lists the CVEs it fixes, the products it applies to, and a PowerShell line to check whether it is installed. When Microsoft lists known issues or changes for an update, the page opens with a Before you deploy box quoting them.
- We follow Microsoft's revisions, not only the first release. The Office for Mac and Android change was a revision to months-old CVEs, which is easy to miss if you only read each month's release. Our pages are checked on every data refresh against CISA's Known Exploited Vulnerabilities catalog and Microsoft's Security Update Guide for exploitation status, incomplete fixes, and the products each recent update names; a page that disagrees on one of those carries a validation warning until it is fixed.
- Exploitation changes reach the site the same day. Every two hours we compare what our live site says with CISA's catalog and Microsoft's exploitation flags, and republish when a Microsoft CVE we cover becomes exploited.
- We are fixing what we found this month. Our CVE pages take their fix list from the KBs Microsoft names, so the Office for Mac and Android editions, which Microsoft lists with release notes instead, are missing, and the pages for these nine CVEs currently show only the core facts. Showing those editions is our next change to those pages.
- Patch state for your own tenant. Senserva's free audits report the patch state of a real Microsoft environment alongside 650+ security checks across Microsoft 365, Intune, Defender, and Entra ID.
To get alerts like the one this post expands on by email, join Senserva Watch; it is free. If you see one of our pages disagree with Microsoft, tell us: Microsoft's page is the reference, and we follow it.
Written by Senserva Trustworthy AI from Microsoft's own publications and CISA's catalog, with every quotation checked against its source and the facts reviewed independently before publishing. The sources behind our feeds, and their terms, are on our data sources page.