
November is a (comparatively) large month. Microsoft’s November 2026 Patch Tuesday fixes 1,240 CVEs, 64 of them rated vital. Begin with Outlook: attackers are already utilizing CVE-2026-124194, a spoofing flaw. A Chromium flaw, CVE-2026-125350, can also be being exploited, and on the time of writing, Microsoft has mounted it solely in Edge for Android. The Readiness workforce recommends that Home windows, Workplace, Change and Microsoft browsers are included in a Patch Now schedule. SQL Server and Microsoft developer instruments can comply with your customary launch schedule. Our infographic exhibits the deployment threat for every product household. Our depend takes Microsoft’s 1,094 CVEs, provides 165 republished Chromium fixes and leaves out 19 Azure and open-source entries.
Recognized points
Excellent news first: the November Home windows 11 updates record no identified points. The three updates are KB5132061, KB5132059 and KB5131087. A number of older points additionally shut this month:
- On-premises Change had a tough October. After the October Home windows Server updates, some servers misplaced Outlook on the net sign-in, left mail within the Outbox or failed mailbox replication. The November server updates repair this: KB5131080 for Home windows Server 2025 and KB5131090 for Home windows Server 2022. Home windows Server 2019 will get KB5131085, and Home windows Server 2016 will get KB5131291.
- Some USB Audio Class 1.0 units which have failed with error code 10 since 8 September ought to begin once more.
- Including a printer revealed in Energetic Listing via Settings works once more, after failing with error 87 since October.
- KB5132061 fixes two October points on Home windows 11 24H2. Sensible App Management could be turned again on, and non-admin Distant Desktop works once more with Administrator safety enabled. 25H2 and 26H2 already had each fixes from the 28 October preview. That preview was KB5127936.
One Home windows Server concern stays open. WSUS nonetheless hides synchronization error particulars on Home windows Server 2025 and 2022. Microsoft made that change to handle CVE-2025-59287, and there’s no revealed workaround. If a sync fails, WSUS won’t inform you why.