Security & identity

November 2026 Patch Tuesday: 1,093 CVEs, Outlook Zero-Day, What to Patch First

Microsoft's November 2026 Patch Tuesday fixes 1,093 CVEs, 63 Critical, plus an exploited Outlook zero-day. KB numbers, known issues and a patch order for admins.

By EpiFive Editorial TeamReviewed/updated 11 min readHow we check our guides
On this page

Microsoft released its November 2026 security updates on Tuesday 10 November 2026. The Security Update Guide data lists 1,093 Microsoft CVEs: 63 Critical, 1,029 Important and 1 Moderate, with one zero-day under active attack, CVE-2026-124194 in Microsoft Outlook. Patch Outlook and Microsoft 365 Apps, Exchange servers and domain controllers first, then the rest of Windows within your normal cycle.

This page is the November entry of the EpiFive Patch Tuesday hub, which lists every month and the date of the next release. All counts below come from Microsoft's own data unless they are marked as reported by someone else.

Who this is for and what you get

This summary is for Windows and Microsoft 365 administrators, small IT teams and managed service providers who need to decide what to deploy this week. By the end you will have the numbers that matter, the KB article for each Windows version, the known issues to test for, and a patch order you can paste into a change request.

November 2026 at a glance

The totals count CVEs that Microsoft itself issued and first published on 10 November 2026, from the machine-readable release (CVRF) behind the Security Update Guide release notes. Microsoft's guide also republishes Chromium (for Edge), Azure Linux and other open-source CVEs; those are not in these numbers, which is why some news totals are higher.

MeasureCount
Microsoft CVEs published 10 November 20261,093
Critical63
Important1,029
Moderate1
Exploited (Microsoft "Exploitation Detected")1
Publicly disclosed before release0
Rated "Exploitation More Likely"42

By impact type, the same 1,093 CVEs split into 535 elevation of privilege, 296 remote code execution, 156 information disclosure, 46 denial of service, 27 security feature bypass, 22 spoofing and 11 tampering. Of the 63 Critical CVEs, 48 are remote code execution and 15 are elevation of privilege.

Reported totals differ. Tenable reported the same 1,093 CVEs. BleepingComputer reported 1,235 flaws with 66 Critical, a count that includes the Microsoft Edge (Chromium) fixes released the same day. Use the Security Update Guide as the authority.

Five Microsoft CVEs were published on other November days: an Entra Device Registration fix on 5 November (a cloud service), an Edge fix on 4 November, a OneNote fix on 11 November, and two SharePoint Server CVEs on 16 November (CVE-2026-124222 and CVE-2026-124223) that are fixed by the same 10 November SharePoint update, KB5002945.

Zero-day: CVE-2026-124194 (Outlook spoofing)

  • What it is: Microsoft describes it as "Product UI does not warn user of unsafe actions in Microsoft Office Outlook". An attacker sends a crafted message file; if the user opens it, Outlook connects to an attacker-controlled network location without the usual external-content warning and can disclose the user's NTLMv2 hash, which the attacker can use to authenticate as that user.
  • Status: Microsoft marks it "Exploited: Yes" ("Exploitation Detected"). It is not publicly disclosed. The Preview Pane is not an attack vector, per Microsoft's FAQ; the user has to open the file.
  • Severity: Moderate, CVSS 3.1 base score 6.5. The low rating does not reduce the urgency: it is being used in attacks now.
  • CISA: added to the Known Exploited Vulnerabilities catalog on 10 November 2026, with a remediation due date of 24 November 2026 for US federal civilian agencies.
  • Affected and fixed versions: Microsoft 365 Apps for Enterprise (see Microsoft's Office security release notes), Office LTSC 2024 (build 16.0.17932.21140) and Office LTSC 2021 (build 16.0.14334.21048).

The same day, CISA also added a Chromium flaw, CVE-2026-125350, to the KEV catalog. Chromium fixes reach Microsoft Edge through Edge's own updates, so check that Edge is current as well.

Critical remote code execution bugs to know

All 48 Critical remote code execution CVEs are listed in the Security Update Guide. These are the ones that change a patch order, either because Microsoft rates them "Exploitation More Likely" or because they need no sign-in and no user action:

CVEComponentCVSSWhy it matters
CVE-2026-118146Active Directory Domain Services8.8Exploitation More Likely; network attack with low privileges
CVE-2026-118207Exchange Server8.8Exploitation More Likely; an authenticated low-privileged attacker can run code on the server
CVE-2026-119952Windows Schannel (TLS)8.1Exploitation More Likely; no authentication
CVE-2026-113862Windows NAT8.1Exploitation More Likely; no authentication
CVE-2026-116928Windows Search component9.8Microsoft says an email attachment that Exchange indexes automatically can trigger it; no user action
CVE-2026-119958Windows LDAP9.8Listed for Windows Server 2016 and Windows 10 version 1607
CVE-2026-112967Windows Xbox Live Networking Service9.8Network attack, no authentication or user action

Other Critical groups: 12 in Excel, 4 in Word, 3 in Outlook, 2 in Office and 1 in PowerPoint (opening a crafted file), 5 in Windows Message Queuing (MSMQ), plus Critical fixes in Windows CredSSP, IIS, Deployment Services, RPC Runtime, TCP/IP, SMB server (srvnet.sys), Print Spooler components, Graphic Fonts and Microsoft Defender (CVE-2026-122194, fixed in Malware Protection Engine 1.1.26100.4, which Defender normally installs automatically). Hyper-V has 8 Critical elevation-of-privilege fixes. Two Critical Azure fixes (Azure OpenAI, CVE-2026-119990, and Azure Managed Grafana, CVE-2026-114160) are marked by Microsoft as needing no customer action.

The RPC Runtime fix (CVE-2026-118737) also starts a behaviour change: Microsoft says Windows updates from 10 November 2026 make clients offer NTLM message signing by default for non-anonymous connections, with a next phase planned for May 2027. Watch for old appliances or file servers that fail when signing is offered.

Products affected

Counts are Microsoft CVEs by product, grouped by EpiFive from the product tags in Microsoft's data:

Product groupCVEs
Windows (all Windows components and roles)731
Office apps: Word 65, Excel 64, Outlook 20, Office 9, PowerPoint 7, Access 7, Visio 2174
Developer tools: VS Code, ASP.NET Core, .NET, Visual Studio, PowerShell, SDKs62
SQL Server (including the JDBC driver)54
SharePoint Server27
Azure services and tools19
Other: Defender, Dynamics 365 on-premises, Configuration Manager, HPC Pack, Xbox, others14
Exchange Server9
Teams3

KB numbers for each Windows version

Each KB below is the November 10, 2026 release listed in Microsoft's update history and the Security Update Guide. Installing the newest cumulative update also installs everything before it.

Windows versionNovember 2026 KBOS build
Windows 11, versions 24H2, 25H2 and 26H2KB513206126100.9974 / 26200.9974 / 26300.9974
Windows 11, versions 24H2, 25H2, 26H2 (hotpatch)KB513204326100.9911 / 26200.9911 / 26300.9911
Windows 11, version 26H1KB513205928000.3501
Windows 11, version 23H2 (Enterprise and Education: last update)KB513108722631.7711
Windows 10, versions 22H2 and 21H2 (ESU and LTSC 2021)KB513109619045.7846 / 19044.7846
Windows 10 version 1809, Windows Server 2019KB513108517763.9487
Windows 10 version 1607, Windows Server 2016KB513129114393.9688
Windows Server 2025KB513108026100.33822
Windows Server 2025 (hotpatch)KB513107726100.33730
Windows Server 2022KB513109020348.5870

Hotpatch devices also get a separate Windows PowerShell security update: KB5135385 for Windows 11 and KB5135386 for Windows Server 2025. It fixes CVE-2026-124224 and CVE-2026-124225 on the hotpatch baseline builds.

Other server products:

ProductNovember 2026 update
Exchange Server Subscription Edition RTMKB5133453
SharePoint Server Subscription EditionKB5002945 (also fixes the two CVEs published 16 November)
Office Online ServerKB5002946
SQL Server 2025 / 2022 / 2019 / 2017GDR or CU security updates per version, listed in each SQL Server CVE
Microsoft 365 Apps, Current ChannelVersion 2610 (Build 20527.20196)
Office LTSC 2024 / LTSC 2021Build 17932.21140 / Build 14334.21048

Windows 11, version 23H2 Enterprise and Education editions reached end of updates on 10 November 2026, so KB5131087 is their last security update. Move those devices to a supported version.

Known issues from Windows release health

Checked on Windows release health on 19 November 2026:

  • SQL Server linked server connections might remain open (Confirmed). After updates from 13 October 2026 and later, SQL Server linked server queries that use OLE DB providers, Oracle and PostgreSQL among them, can leave connections open, which can slow the server over time. Microsoft lists Windows 11 versions 23H2 through 26H2 (and 26H1), Windows 10 version 1809 and Enterprise LTSC 2019, and Windows Server 2012 through 2025. Microsoft offers a mitigation through Microsoft Support for business and says an out-of-band fix is coming.
  • SLMGR activation error 0x80041008 (fixed out of band). On 13 November 2026 Microsoft released optional out-of-band updates for some enterprise devices where slmgr.vbs licensing operations, such as KMS setup, fail after the November update: KB5136489 (Server 2025), KB5136487 (Server 2022), KB5136490 (Server 2019 and Windows 10 LTSC 2019), KB5136483 (Windows 11 23H2) and KB5136493 (Windows 10 22H2 ESU and LTSC 2021). Already-activated devices stay activated.
  • Resolved by the November update: the Exchange Server issue where users could not sign in to Outlook on the web or mail stayed in the Outbox after the October update (listed on the Windows Server 2022 and 2025 pages), and USB Audio Class 1.0 devices failing with Code 10 after the September update.

What to patch first

  1. Outlook and Microsoft 365 Apps for CVE-2026-124194, the exploited zero-day. Check that every client is on a November build, including Office LTSC volume-licensed installs, which do not update from the Microsoft 365 channel.
  2. Exchange servers: install Exchange SU KB5133453 for CVE-2026-118207 and the Windows cumulative update for the Windows Search flaw CVE-2026-116928, which Exchange can trigger by indexing an attachment.
  3. Domain controllers for the AD DS fixes (CVE-2026-118146 and the Critical elevation of privilege CVE-2026-118148), after a short test with one DC per site.
  4. Internet-facing and edge servers: IIS, RD Gateway, servers doing TLS with Schannel, NAT and anything running Message Queuing.
  5. Hyper-V hosts, then file, print and SharePoint servers (KB5002945).
  6. All Windows clients in normal rings; SQL Server hosts after testing linked servers.
  7. Developer machines: VS Code, Visual Studio, .NET and PowerShell updates.

How to deploy the November updates

  • Microsoft Intune: Windows quality updates follow your update rings; for urgent cases use an expedited quality update policy. See Intune update rings and Windows hotpatch and Microsoft's guide to expediting Windows quality updates.
  • Windows Autopatch: the November release flows through your Autopatch rings automatically; use Autopatch's expedite option if you need the zero-day fix sooner.
  • WSUS / Configuration Manager: approve the November cumulative updates for each product and classification; the Microsoft 365 Apps and Exchange updates are separate. Microsoft's WSUS documentation covers approvals and synchronization.
  • Azure Update Manager for Azure and Arc-enabled servers: see patching Arc servers with Azure Update Manager.
  • Feature updates: if some PCs are still on Windows 11 23H2 Enterprise, plan the move with the Intune feature update guide.

After deployment, check the OS build with winver or:

Get-ComputerInfo -Property OsName, OsVersion, OsBuildNumber

The build should match the table above or be higher (for example 26200.9974 or later on version 25H2).

What we checked

  • Downloaded Microsoft's November 2026 security update release (CVRF 2026-Nov) from the MSRC API on 19 November 2026 and counted the CVEs that Microsoft issued and first published on 10 November: 1,093 (63 Critical, 1,029 Important, 1 Moderate), with exactly one "Exploitation Detected" flag (CVE-2026-124194) and no "Publicly Disclosed: Yes".
  • Cross-checked the zero-day against CISA's KEV catalog feed (version 2026.11.18): CVE-2026-124194 added 10 November 2026, due 24 November 2026.
  • Matched each Windows KB and OS build in the Security Update Guide data against the titles of the November 10, 2026 KB articles on support.microsoft.com.
  • Read the Windows release health pages for Windows 11 25H2 and 26H2, Windows 10 22H2, Windows Server 2025 and 2022, and the Windows message center, on 19 November 2026.
  • Compared our total with reported totals from Tenable (1,093) and BleepingComputer (1,235, which includes Edge fixes) and noted the difference instead of picking one.
  • Not tested: we did not install the updates on test machines; deployment steps follow Microsoft's documentation as of 19 November 2026.

Last tested: 2026-11-19

References

Questions people ask

How many vulnerabilities did Microsoft fix on November 2026 Patch Tuesday?

Microsoft's Security Update Guide data for 10 November 2026 lists 1,093 Microsoft-issued CVEs: 63 Critical, 1,029 Important and 1 Moderate. Some outlets report higher totals, such as 1,235, because they also count Chromium, Azure Linux and other third-party CVEs that Microsoft republishes in the same guide.

Is there a zero-day in the November 2026 Patch Tuesday?

Yes, one. CVE-2026-124194, a Microsoft Outlook spoofing vulnerability, is marked "Exploitation Detected" by Microsoft and was added to CISA's Known Exploited Vulnerabilities catalog on 10 November 2026. Opening a crafted file can make Outlook connect to an attacker's server without the usual warning and leak the user's NTLMv2 hash. No CVE was marked publicly disclosed this month.

What is the November 2026 cumulative update for Windows 11?

KB5132061 for Windows 11 versions 24H2, 25H2 and 26H2 (OS builds 26100.9974, 26200.9974 and 26300.9974), KB5132059 for version 26H1 (build 28000.3501) and KB5131087 for version 23H2 (build 22631.7711). Hotpatch devices get KB5132043 instead.

Are there known issues with the November 2026 updates?

Microsoft lists a confirmed issue where SQL Server linked server connections to databases such as Oracle and PostgreSQL stay open after updates from 13 October 2026 and later. On 13 November Microsoft also released optional out-of-band updates for an SLMGR activation error 0x80041008 on some enterprise devices.

Patch TuesdayWindows UpdateMicrosoft OutlookExchange ServerMicrosoft Intune