Microsoft’s November 2026 Patch Tuesday landed on Tuesday, November 10, and it is one of those updates you should not put off until the weekend. The release fixes 1,094 vulnerabilities across Windows, Office, Exchange, Azure, and Xbox. Sixty-three of them are rated Critical. One is already being exploited in the wild. And two of the worst flaws need no click, no login, and no user interaction at all.
Most patch days blur together into the same routine: a big number, a few scary CVE IDs, and the usual advice to update. This month is different in one specific way. The single exploited bug in the whole release is rated only Moderate, with a CVSS score of 6.5. On paper it looks forgettable. In practice it is the one attackers are already using to steal login credentials, and the fix for it does not even arrive with the normal Windows update. That is the kind of detail that catches people out, so here is what actually matters.
The one bug attackers are already using: Outlook’s NTLM hash leak
The exploited flaw is CVE-2026-124194, a spoofing vulnerability in Microsoft Outlook. Here is how it works in plain English: an attacker sends you a specially crafted message file, and if you open it, Outlook quietly connects to a server the attacker controls, without showing the usual warning about external content. That connection hands over your NTLMv2 hash, which is effectively a scrambled version of your Windows login credential. With it, an attacker can try to impersonate you on a network.
Microsoft has confirmed the flaw is being exploited, and CISA has added it to its Known Exploited Vulnerabilities catalog, giving federal agencies until November 24 to patch. Two details are worth knowing. First, the Preview Pane is not an attack vector here, so simply receiving the message does not hurt you; you have to open the crafted file. Second, and this is the catch, the Outlook fix does not come with the Windows cumulative update. It ships through the Microsoft 365 Apps and Office LTSC updates instead, which means updating Windows alone leaves Outlook exposed. A 6.5-rated bug getting exploited while 9.8-rated flaws sit untouched is a good reminder that severity scores measure how bad a flaw could be, not how likely someone is to use it.
The zero-click flaw that needs no click at all
The scariest patch in this release is CVE-2026-116928, a remote code execution flaw in the Windows Search component, rated Critical at CVSS 9.8. It is a genuine zero-click vulnerability, and the attack path is almost absurdly simple. An unauthenticated attacker sends an email containing a specially crafted attachment. When the message reaches an Exchange server, the server automatically indexes the attachment for search, and that indexing process triggers the flaw. The recipient never opens the email. They never open the attachment. They never click anything. The code just runs, with the permissions of the processing service.
The Zero Day Initiative called it a zero-click code execution bug on a high-value target, and rated it more severe than any of the nine Exchange patches in this month’s release. It is also on ZDI’s list of 30 potentially wormable flaws in this batch, meaning a successful exploit could in theory spread on its own. Microsoft rates exploitation as less likely for now, and nobody has reported attacks using it yet, but the shape of this bug is exactly the kind security teams lose sleep over: no user action, no authentication, and a mail server doing the attacker’s work for them.
If you run Exchange Server in your organization, this is the patch to prioritize. If you are a home user, the same fix rides along in the normal Windows cumulative update, so installing it covers you.
The other 9.8s hiding in this month’s release
The Windows Search flaw is not the only maximum-severity issue this month. Several of them sit on core network services that are reachable without any login at all.
| CVE | Component | CVSS | Why it matters |
|---|---|---|---|
| CVE-2026-116928 | Windows Search / Exchange | 9.8 | Zero-click code execution via emailed attachment indexing |
| CVE-2026-119958 | Windows LDAP | 9.8 | Unauthenticated remote code execution, no user interaction |
| CVE-2026-85844 | Windows Kerberos | 9.8 | Privilege escalation on core authentication service |
| CVE-2026-88218 | Windows DNS | 9.8 | Remote code execution on DNS servers |
| CVE-2026-88243 | Windows DHCP Server | 9.8 | Remote code execution via crafted network traffic |
| CVE-2026-88234 | Windows iSCSI | 9.8 | Remote code execution on storage services |
| CVE-2026-112967 | Xbox Live Networking Service | 9.8 | Heap overflow, remote code execution |
| CVE-2026-119990 | Azure OpenAI | 9.8 | Elevation of privilege in the cloud |
| CVE-2026-120002 | SharePoint Server | 9.9 | Elevation of privilege, the highest score this month |
A few more numbers put the month in perspective. Twenty of the patched flaws are remote code execution bugs in Outlook alone. The Windows product family accounts for 726 of the 1,094 fixes. And the Schannel remote code execution flaw, CVE-2026-119952, scored 8.1 but carries Microsoft’s “Exploitation More Likely” tag, which is often a better predictor of real-world trouble than the raw score. If you manage servers, the priority order is straightforward: domain controllers and anything running DNS, DHCP, LDAP, or Exchange first, then everything else.
What to update first, and the Outlook catch
For most home users, the advice is boring and correct: install the November updates and restart. But this month has one extra step that is easy to miss, so here is the short version.
First, open Settings, go to Windows Update, and install the November 2026 cumulative update. That covers the Windows Search flaw, the LDAP flaw, and the rest of the Windows-side fixes. Restart when it asks you to, because the fixes do not take effect until you do. Second, update Office. The Outlook fix travels with the Microsoft 365 Apps or Office LTSC update, not with Windows, so open any Office app, go to Account, and check for Office updates. Outlook 2016 is also on the affected list, so do not assume an older version is safe. Third, if you are responsible for servers, patch domain controllers and Exchange first, and remember that Exchange Server Subscription Edition needs its own update, KB5133453, on top of the Windows cumulative update.
The Outlook bug was already being exploited before Microsoft shipped the fix, so every day you wait is a day the only defense is not opening strange message files. That is not a great defense.
Why this month’s number is so big
At 1,094 fixes, November is the second month in a row with more than 1,000 vulnerabilities patched, after October’s roughly 1,474, the largest Patch Tuesday on record. The number needs context: Microsoft has been steadily expanding what it counts and discloses, and a large share of these flaws are elevation-of-privilege issues that need an attacker to already have a foothold. The count is not the story. The story is that 63 of them are Critical, 30 are potentially wormable according to ZDI, and one is already being exploited. The next Patch Tuesday is December 8, 2026, and between now and then, the only thing standing between your machine and the flaws above is whether you installed this update.
It is also worth remembering that this is not an isolated event. We have had a steady run of serious flaws lately, from the PHP2Shell vulnerability in October to the 9.8 Linux kernel flaw that Ubuntu and Red Hat were still patching, and even the SMS of Death flaw that could crash Android phones with a single text. Patching is no longer a once-a-quarter chore. It is a monthly habit, and the months are getting busier.
Frequently asked questions
What is Microsoft November Patch Tuesday 2026?
It is Microsoft’s monthly security release for November 2026, published on Tuesday, November 10. It fixes 1,094 vulnerabilities across Windows, Office, Exchange, Azure, and Xbox, including 63 rated Critical and one flaw already being exploited.
Which November 2026 Patch Tuesday flaw is being exploited?
CVE-2026-124194, a spoofing flaw in Outlook rated CVSS 6.5. Opening a crafted message file makes Outlook connect to an attacker-controlled server without its usual warning, leaking the user’s NTLMv2 hash. CISA added it to its Known Exploited Vulnerabilities catalog with a November 24 patch deadline for federal agencies.
What is the zero-click Windows Search vulnerability?
CVE-2026-116928 is a Critical remote code execution flaw (CVSS 9.8) in the Windows Search component. An unauthenticated attacker emails a crafted attachment, and Exchange Server indexes it automatically, triggering the flaw with no click and no user interaction. The November Windows cumulative update fixes it.
Do I need to update Office separately from Windows?
Yes, this month. The Outlook fix ships through Microsoft 365 Apps and Office LTSC updates, not through the Windows cumulative update. Updating Windows alone leaves Outlook exposed, so check for Office updates too.
Is the November 2026 Patch Tuesday safe to install?
Yes. These are Microsoft’s official security updates, and the risk of leaving known flaws unpatched is far higher than the risk of installing the patches. Install the Windows cumulative update and the Office update, then restart your PC.

[…] Microsoft’s November Patch Tuesday landed the same week, fixing 1,094 flaws including an exploited Outlook bug and a zero-click Windows Search flaw. […]
[…] the Windows side, Microsoft’s November Patch Tuesday fixed 1,094 flaws, including a zero-click Windows Search vulnerability and an Outlook bug already […]