Skip to content
Microsoft November 2026 Patch Tuesday: 1,094 CVEs [2026]

Microsoft November 2026 Patch Tuesday: 1,094 CVEs [2026]

Shattered • November 11, 2026

Microsoft’s November 2026 Patch Tuesday fixed 1,094 CVEs on November 10 and included one flaw attackers were already using: CVE-2026-124194, an Outlook spoofing bug that can leak a user’s NTLMv2 password hash. Microsoft rates it Moderate with a CVSS score of 6.5. It is the only exploited zero-day in the release.

The monthly count fell from October’s record, yet it still sits far above anything admins saw earlier this year. Splashtop puts October at 1,413 CVEs and September at 974. Microsoft has not said who is attacking Outlook, when the attacks began or how widespread they are, so defenders are patching with little threat context.

The headline total matters less than the order of work. For the third month running, the bug attackers actually use carries a rating below Critical. That pattern is why a Patch Tuesday triage routine built around exploit status beats one built around severity labels. The Outlook NTLM hash leak is the clearest example yet.

Don't miss new tech stories on Google

Add Shattered once in the Google app and our stories show up in your news suggestions.

What Microsoft Shipped in the November 2026 Patch Tuesday

Microsoft’s release notes list 1,094 CVEs across Windows, Microsoft 365 and Office apps, SQL Server, SharePoint Server, Exchange Server, Azure, Defender and developer tools. Severity ratings cover 1,093 of them. Of those, Microsoft rated 63 Critical, 1,029 Important and 1 Moderate. The single Moderate entry is the exploited Outlook flaw.

No CVE in the release was publicly disclosed before the patch landed. That means defenders had no public proof-of-concept to study ahead of time. Splashtop also notes that Microsoft republished 165 non-Microsoft CVEs this month, up from one in October. Those entries inflate the raw count without adding Microsoft-authored fixes, which is worth remembering when you compare totals across months.

Among the 63 Critical flaws, 48 are remote code execution bugs and 15 are elevation of privilege bugs. Action1’s Jack Bicer, quoted by CSO Online , counts four at CVSS 9.8 and says three of those four need no credentials and no user action.

CVE-2026-124194: How the Outlook NTLM Leak Works

An unauthenticated attacker sends a specially crafted message file and persuades the recipient to open it in Outlook. Opening the file makes Outlook connect to an attacker-controlled network location without showing the usual external-content warning. That connection hands the attacker the victim’s NTLMv2 hash. The attacker can then relay the hash to other systems to sign in as the user, or crack it offline to recover the password.

The attack chain in plain steps

The attacker delivers a crafted message file by email or any other channel that puts it in front of the target.

The victim opens the file in Outlook, which takes a deliberate click.

Outlook silently reaches out to an attacker-controlled network location and skips the external-content warning.

The connection leaks the NTLMv2 hash.

The attacker relays or cracks the hash and impersonates the user.

The missing warning is the real flaw. Outlook normally flags content that pulls from outside the organization, and users and mail gateways lean on that prompt. Here the prompt never appears, so a file that would look suspicious under normal behavior looks routine.

Why the Preview Pane note matters

Reporting based on Microsoft’s description says the bug cannot be triggered through Outlook’s Preview Pane. The victim has to open the file. That narrows the attack from a zero-click scenario to a one-click one, which still works against a busy inbox. It also means user training and attachment filtering buy some real protection until the update is installed, though neither replaces the patch.

The pattern echoes other file-opening bugs defenders have chased this year, such as the Windows Shell zero-day that bypassed Mark of the Web . In both cases the attacker needs the user to touch a file, and in both cases the built-in warning is what fails.

Why a CVSS 6.5 Outlook Zero-Day Gets the Top Slot

CVSS measures how bad a flaw could be under assumptions. Exploit status measures what attackers are doing today. Microsoft has confirmed exploitation of CVE-2026-124194 before the fix shipped, which beats every theoretical Critical in the release for patch-first treatment. Nick Carroll, cyber incident response manager at Nightwing, told CSO Online that the low score should not fool anyone.

Splashtop makes the same point: this is the only Moderate-rated CVE in the entire release, yet it is the one attackers are confirmed to be using. The gap between score and reality repeats a lesson from earlier this year, when a VMware ESX zero-day rated just 2.7 landed on CISA’s exploited list. Teams that sort queues by CVSS alone will bury these bugs under hundreds of higher-scored entries.

The lesson sharpens when volume is this high. With 1,094 CVEs in one cycle, a severity-first queue puts 63 Critical items ahead of the one under attack. An exploit-first queue starts with a single line item. The CVSS versus CISA KEV comparison shows how wide that gap runs across the wider vulnerability population.

Which Products Get the Fix, and the LTSC 2021 Question

Reported affected products include Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024. The fix ships through the Microsoft 365 Apps and Office LTSC security updates. It does not ship in the Windows cumulative update alone. Splashtop names that cumulative update as KB5132061, so organizations that deploy only Windows updates through WSUS or a similar channel stay exposed until the Office update lands.

One detail deserves a flag. Microsoft’s lifecycle notice says Office LTSC 2021 reached end of support on October 13, 2026, along with Project LTSC 2021 and Visio LTSC 2021. Yet the reporting lists LTSC 2021 among the products receiving the November fix, and Microsoft’s release notes show a build dated October 13 as the newest in that update history. The sources do not reconcile the two. Admins running LTSC 2021 should check Microsoft’s advisory directly and plan a move, since Microsoft names Office LTSC 2024 as the current on-premises release, with support reportedly running to October 2029.

For subscription customers the story is simpler. Microsoft 365 Apps remains an actively supported, continuously updated product, and its enterprise channel releases carry security fixes. Microsoft also began merging the Semi-Annual Enterprise Channel and Monthly Enterprise Channel in July 2026, so channel names in your update tooling may not match the ones in older runbooks.

Counting the Flaws: 1,094, 1,093 or 1,235

Headlines this week quote three different totals, and all three are defensible. Splashtop, CSO Online and Action1 use 1,094, the figure in Microsoft’s release notes. Splashtop notes that severity ratings cover only 1,093, and Tenable’s headline uses 1,093 as well. BleepingComputer reports 1,235, and Blackpoint Cyber explains why: its count includes 142 Microsoft Edge vulnerabilities.

The scopes differ, not the facts. If you report patch volume to leadership, pick one number, name its scope and stick with it. Microsoft’s own release notes use 1,094, as do most outlets that counted Microsoft product CVEs, including SecurityWeek in its headline.

Where the 1,094 CVEs Sit

Windows accounts for roughly two-thirds of the release. Office and SharePoint Server add 201 more, which keeps document-based risk high on the list. The table below uses Splashtop’s product family breakdown for the Microsoft November 2026 Patch Tuesday.

The vulnerability types lean heavily toward privilege and code execution. Elevation of privilege and remote code execution together make up 76% of the severity-rated release, and Splashtop’s counts show the split.

The zero-day sits in one of the smallest buckets. Spoofing accounts for just 22 CVEs, and the one under attack is among them. A team that skimmed the volume leaders, elevation of privilege and remote code execution, would still need to go looking for it.

The 63 Critical Flaws Behind the Zero-Day

Bicer’s three no-interaction flaws are worth naming. The Windows LDAP remote code execution bug (CVE-2026-119958) lets an unauthenticated attacker run code in the LDAP service, which puts domain controllers and Active Directory at risk. The Exchange Server remote code execution bug (CVE-2026-118207) can be triggered by anyone able to send email to the organization. The Xbox Live Networking Service bug (CVE-2026-112967) gives an attacker on the same network full control of a Windows system. The fourth 9.8 flaw, an Azure OpenAI elevation of privilege bug (CVE-2026-119990), is patched automatically by Microsoft. Scores vary by source, and Splashtop lists the Exchange flaw at CVSS 8.8, so check the advisory for the number your policy uses.

Splashtop groups the remaining Critical items by infrastructure. Identity and directory services carry Active Directory Domain Services, LDAP, Schannel, CredSSP and TPM flaws. Network-facing services carry Message Queuing, SMB Server, TCP/IP, NAT and RPC Runtime bugs. Windows Hyper-V has eight Critical elevation of privilege vulnerabilities, a concentration that makes hypervisor hosts a patching priority because one escaped guest threatens every tenant on the host.

Office applications account for 22 Critical remote code execution flaws: 12 in Excel, 4 in Word, 3 in Outlook, 2 in shared Office components and 1 in PowerPoint. The three Critical Outlook bugs are not marked as exploited, but they ship in the same Office update as the zero-day fix, so one Office rollout closes both sets. SharePoint Server gets a separate mention: CVE-2026-120002 is rated Important yet scores CVSS 9.9, another case where the label understates the risk.

Same-Week Patches From Chrome, SAP, Adobe and Mozilla

Microsoft was not the only vendor shipping urgent fixes. Google patched a second exploited zero-day, CVE-2026-125350, a use-after-free in Chrome’s XML component. Splashtop reports the fix is in Chrome 157.0.8103.50/.51 and Extended Stable 156.0.8078.96, and that CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10, the same day as the Outlook bug. CSO Online, citing Ivanti’s Chris Goettl, counts it as Chrome’s eighth zero-day of 2026. Chrome applies updates only after a relaunch, so check installed versions rather than download status. Chromium-based browsers such as Edge need the fix as well.

SAP shipped patches for 35 vulnerabilities, four of them critical at CVSS 10.0, per Blackpoint. Two of the four form the flaw pair researchers at Onapsis call ICM2Shell, a memory corruption bug in how the SAP Kernel handles WebSocket traffic. Onapsis says it gave SAP a working exploit for unauthenticated remote code execution. Because WebSocket support is on by default in the Internet Communication Manager and the Web Dispatcher, a system is exposed even if no application uses WebSocket.

Adobe’s Connect update (APSB26-191) holds 24 CVEs, 18 of them critical and six rated CVSS 10.0. Adobe says it knows of no exploitation. Adobe ColdFusion 2021 also reached the end of extended support on November 10, according to Splashtop, with its last update shipping in December 2025. Any leftover ColdFusion 2021 servers now need an upgrade plan, not a patch.

Operational Impact for IT and Security Teams

The practical burden of the November 2026 Patch Tuesday falls on endpoint teams. Windows alone carries 726 CVEs, but the zero-day lives in the Office update channel, so a team that patches the operating system on schedule can still leave the exploited flaw open. Organizations that split Windows servicing and Office servicing between different teams or tools face the biggest risk of a gap.

Federal agencies have a clock. Splashtop reports CISA’s remediation due date for CVE-2026-124194 is November 24, 2026, two weeks after the listing. Private-sector teams are not bound by that deadline, but it works as a reasonable service-level target. Other recent listings came with different clocks, such as a WordPress flaw due November 6 and the 3-day deadline on a FortiMail zero-day .

Credential exposure widens the blast radius beyond one machine. If an attacker relays a leaked NTLMv2 hash successfully, the intruder inherits whatever that user can reach on file shares, internal web apps and any service that still accepts NTLM. That is why Blackpoint recommends blocking outbound SMB on TCP port 445 at both the endpoint and the network perimeter, so the control follows roaming users off the corporate network.

Historical Context: Three Months of Record Volume

The last three Patch Tuesdays tell the story. September’s release of 974 CVEs set what looked like a record at the time, as covered in our report on the September release with two exploited zero-days . October then jumped to 1,413 by Splashtop’s count (Action1 counts 1,409), detailed in the October Patch Tuesday report . The November 2026 Patch Tuesday total of 1,094 is the second-largest release to date, ahead of September.

The exploited bug has been rated below Critical in each of those three months, according to Splashtop. That is a small sample, but it fits a long-running pattern: attackers prefer reliable bugs in widely deployed software over the loudest ones. A hash-leaking Outlook flaw fits that profile. It needs one click, reaches multiple Office channels and produces credentials that unlock other systems.

Microsoft’s own tooling shapes the volume. CSO Online reports that Microsoft has used its AI model to find thousands of vulnerabilities in its products since the summer, and that the company credited an Anthropic researcher using the Claude AI assistant for finding the Outlook flaw. Tenable’s Satyam Narang, per the same report, described it as the first time AI-driven discovery found a needle after months of building bigger haystacks. The Claude credit rests on CSO Online’s reporting, and we could not confirm it in Microsoft’s own advisory text.

Expert Views on the AI-Driven Bug Flood

Defenders disagree on how to respond to the volume. Dustin Childs, head of threat awareness at TrendAI’s Zero Day Initiative, argues for dropping broad triage and acting at once on Exchange and domain controllers (LDAP and Kerberos), ring-fencing exposed network services like DNS and DHCP to stop wormable spread, and verifying manual fixes on cloud services. His concern is zero-click compromise.

Tyler Reguly, associate director of security research and development at Fortra, takes a calmer line. He expects elevated counts to continue while Microsoft fixes long-hidden bugs that AI is now surfacing, followed by a decline once that backlog clears. He also warns CSOs that vendors may hype unimportant vulnerabilities because it markets their services, and says a flaw is not critical if you do not run the affected software. His advice is to keep a prioritization process that already works and to invest in hardening and mitigation over chasing every CVE.

Both views hold up. Childs’s list targets the flaws that need no user action, and Reguly’s caution targets the noise. The Outlook zero-day sits between them: it needs a click, but it is already under attack. A sensible reading is to patch Outlook first because exploitation is confirmed, then follow Childs’s order for the unauthenticated network bugs, then apply Reguly’s exposure test to everything else.

What Defenders Should Do in the 72 Hours

Splashtop’s tiering gives a workable starting point, and the table below adjusts it for exposure. Push the Office update for CVE-2026-124194 to every device running Outlook first. Then move to domain controllers, Exchange and anything internet-facing. Confirm Chrome has relaunched on version 157.0.8103.50 or later.

Beyond patching, three controls cut the risk from this specific bug. Block outbound SMB on TCP 445 at the endpoint and the perimeter. Review which accounts still authenticate with NTLM and move what you can to Kerberos. Tighten attachment filtering for message files from outside the organization. None of these replaces the update, but each shrinks what a leaked hash is worth.

Predictions for the Three Patch Cycles

These forecasts are our own analysis of the numbers above and not statements from any vendor or researcher.

Volume stays high. With September at 974, October at 1,413 and November at 1,094, we expect the Patch Tuesday after the November 2026 Patch Tuesday to land above 900 CVEs. A drop below that floor would suggest the AI-found backlog is clearing faster than Fortra’s Reguly expects.

Another sub-Critical zero-day appears. Attackers have favored bugs below the Critical line three months running, and we expect that to hold for at least one more cycle.

Credential-leak bugs draw more attention. Researchers will look harder for other Office paths that reach out over SMB or HTTP without a warning, and more such findings will surface in the coming months.

Office servicing gets its own audit line. Because the fix skips the Windows cumulative update, compliance teams will start tracking Office build compliance separately from OS patch compliance.

NTLM exposure becomes a standing risk item. Expect more enterprise policies to restrict outbound NTLM, driven by incidents like this one.

For ongoing tracking of exploited flaws and vendor advisories, see our wider security coverage .

What is CVE-2026-124194? It is a Microsoft Outlook spoofing vulnerability fixed in the November 10, 2026 Patch Tuesday release. Microsoft rates it Moderate with a CVSS score of 6.5 and says it was exploited before the update shipped. Opening a crafted message file can leak the user’s NTLMv2 hash.

How many vulnerabilities did Microsoft fix in November 2026? Microsoft’s release notes count 1,094 CVEs, with 63 rated Critical. Severity ratings cover 1,093 of them. Some outlets report 1,235 because their count includes Microsoft Edge vulnerabilities.

Can the Outlook flaw trigger from the Preview Pane? Reporting based on Microsoft’s description says no. The victim has to open the crafted message file, so the attack needs one click.

Does the Windows cumulative update fix the Outlook zero-day? No. Splashtop reports the fix ships in the Microsoft 365 Apps and Office LTSC 2021 and 2024 security updates and not in the Windows cumulative update (KB5132061). Install the Office update separately.

When is the federal deadline to patch it? According to Splashtop, CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10, 2026, with a remediation due date of November 24, 2026 for federal agencies.

Is there a second zero-day this week? Yes, in Google Chrome. CVE-2026-125350 is a use-after-free in Chrome’s XML component, fixed in Chrome 157.0.8103.50/.51. Relaunch the browser to apply the update, and watch for fixes in other Chromium-based browsers.

Who is behind the attacks on Outlook? Microsoft has not said. The reporting we reviewed does not name the attackers, the start date of the campaign or any post-exploitation activity.