Microsoft released its November security updates on Tuesday, November 10, and one of the flaws in them is already being used in real attacks. It is not the biggest bug of the month and it does not carry the scariest score. It is a moderate-rated Outlook flaw that can leak a person's Windows password hash, and the fix reaches a PC through Office, not through Windows Update. Here is what shipped, what is being exploited, the short list of fixes that matter in an office, how we patch, and what your staff should do. CISA's deadline for federal agencies to patch the Outlook flaw is Tuesday, November 24, which is a good date to borrow for your own.
What this month means for a small business
The blind spot this month is the green checkmark. Windows Update says the computer is up to date, and an owner reasonably concludes it is patched. But the one flaw being exploited lives in Outlook, and Outlook gets its fixes through the Office update channel. Digital Citizen's write-up is explicit that Office updates separately from the Windows cumulative update, and that is where this fix lives. A machine can be fully current on Windows and still be running the vulnerable Outlook.
The second blind spot is the size. This is the second four-digit Patch Tuesday in a row, and a 1,000-fix month sounds like a 1,000-alarm month. It is not. Of everything Microsoft published, one flaw is confirmed to be under attack, and it needs a person to open a file. Another 42 are flagged as more likely to be exploited, which is the list to work from. The rest are bugs in corners of Windows and Office that nobody in a packing shed, a clinic, or a dispatch office will ever touch directly.
The third is the word "hash." Most owners have never heard it, and it is the whole story this month. When you sign in to a Windows computer, the machine does not pass your password around. It uses a scrambled version of it, called an NTLMv2 hash, to prove who you are on the network. Anyone who captures that hash can do one of two things, as Dark Reading's analysis lays out: replay it to sign in as you somewhere else, or crack it offline to recover the password itself. Short or reused passwords crack quickly. That is why a flaw rated only Moderate is still worth acting on.
The one flaw being exploited: an Outlook file that leaks your password hash
CVE-2026-124194 is a spoofing flaw in Outlook. Microsoft rates it Moderate with a CVSS score of 6.5, and its own exploitability field reads "Exploitation Detected." The attack is ordinary phishing with an unusual payload. An attacker sends a crafted file and persuades someone to open it. When it opens, Outlook reaches out to a location the attacker controls without showing the usual external-content warning, and that connection can leak the person's NTLMv2 hash. Dark Reading notes it may not allow code execution on its own, which is why the score is modest. The consequence is not modest: a captured hash is a path to a real account.
Two details worth knowing. First, Digital Citizen reports that Microsoft says the Preview Pane is not an attack vector for this flaw, so the file has to be opened rather than merely viewed. Second, the affected products listed are Microsoft 365 Apps, Office LTSC 2021, and Office LTSC 2024. The reports we read do not break out which Outlook apps are covered, so if your team uses desktop Outlook, assume this applies to you and check.
CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10, with a November 24 deadline for federal agencies. That deadline does not bind a small business, but it is a useful yardstick: CISA gave federal agencies two weeks for this one.
The fix comes through Office. In Outlook, go to File, Office Account, Update Options, then Update Now. For the person who looks after your systems, the patched builds are 16.0.14334.21048 for Office LTSC 2021 and 16.0.17932.21140 for Office LTSC 2024, per IT-Connect and Digital Citizen. Neither report gives a build for Microsoft 365 Apps, so verify that the update applied rather than comparing numbers.
The fixes that matter, at a glance
Out of more than 1,000 items, this is the short list we are actually working from. CVSS is the industry's 0-to-10 severity score; "exploited" is whether Microsoft confirms real-world attacks.
| CVE | Product | Why it matters | Exploited? |
|---|---|---|---|
| CVE-2026-124194 | Outlook (Microsoft 365 Apps, Office LTSC 2021 and 2024) | Leaks the user's Windows password hash when a crafted file is opened. Moderate, CVSS 6.5. Fixed through the Office update, not Windows Update. | Yes. On CISA's KEV list. |
| CVE-2026-116928 | Windows Search (reached through on-premises Exchange) | CVSS 9.8. A crafted email attachment triggers code execution when Exchange indexes it, so nobody has to open it. Fixed in the Windows cumulative update, not the Exchange update. | No |
| CVE-2026-118207 | Exchange Server Subscription Edition | CVSS 8.8. A logged-in attacker with a low-level account can run code with no user action. Exchange often holds broad rights in Active Directory, so a foothold here reaches well past mailboxes. Update KB5133453. | No |
| CVE-2026-119958 | Windows LDAP (domain controllers) | CVSS 9.8. Crafted network requests can run code with no login and no user action. Microsoft rates exploitation less likely, but it is the one to push to domain controllers first. | No |
| CVE-2026-118146 and CVE-2026-118148 | Active Directory | CVSS 8.8 and 7.5. A logged-in, low-privilege user can run code or gain SYSTEM rights on a domain controller. Microsoft rates both exploitation more likely. | No |
| CVE-2026-120002 | SharePoint Server (on-premises) | CVSS 9.9. A low-privileged account can gain higher privileges over the network with no user interaction. Matters only if you run SharePoint on your own server. | No |
| CVE-2026-85844, 88218, 88243, 88234, 116945 | Kerberos, DNS, DHCP Server, iSCSI, SQL Server | Five more server-role flaws, each rated 9.8. Reachable over the network, which puts domain controllers and any server running these roles at the front of the line. | No |
| CVE-2026-109469 | Entra Device Registration (cloud service) | CVSS 10.0, the score that will top any list sorted by severity. It is a service Microsoft runs, so there is no installer. The reports we read do not identify a customer step; any step would be in Microsoft's advisory. | No |
How many fixes, and why the number keeps changing
Microsoft's release notes list 1,094 CVEs for November 10. IT-Connect and SecurityOnline report 1,093, other trackers land at 1,090 to 1,092, and one outlet reported 1,235. Outlets count differently, so the headlines do not match. We lean on the lower, conservative figure and say "more than 1,000," because the exact count does not change what anyone should do. Sixty-three are rated Critical, and Microsoft flagged 42 others as more likely to be exploited, per SecurityOnline. Elevation of privilege bugs lead the breakdown by a wide margin.
The volume keeps climbing for the reason we covered when an AI model found 271 vulnerabilities in Firefox: automated bug-hunting finds flaws in bulk, mostly in deep, rarely used code. July hit 570, August 400, September 966, and October cleared 1,400. The count of flaws actually being used in attacks is the number that matters, and it is one this month.
Our own filter is the one the table above follows. Exploited first. Then anything Microsoft rates more likely to be exploited. Then anything reachable from the internet with no login. Then anything that fires without a click. Everything else gets installed on schedule and verified, which is what a patch management process is for.
Support dates that moved this month
- Windows 11 version 23H2, Enterprise and Education editions, got its final update. The November update is the last one for those editions; Home and Pro editions of 23H2 were already out of support. If a PC is still on 23H2, the fix is a free move to Windows 11 version 25H2 or 26H2. We schedule feature upgrades as their own pass so they never land on a workday.
- .NET 8 and PowerShell 7.4 LTS moved past their end-of-support date this month. This matters if a line-of-business application or an in-house script was built on them. Ask the vendor or developer for the upgrade plan before an unsupported runtime becomes the weakest part of the stack.
- The next Patch Tuesday is December 8, 2026. That is the last one of the year.
For machines still on Windows 10, the same rule from last month holds: the monthly update only reaches those enrolled in Extended Security Updates. The Windows 10 ESU post lays out the options.
How we roll out patches
We do not push a monthly release to production the day it ships. Patches occasionally break things, and when they do, the industry finds out within a day or two as millions of machines install them. This month that is not hypothetical: the October Windows Server updates broke Outlook on the web and email sending for some on-premises Exchange servers, and the November updates are what fix it, per IT-Connect. A short soak period before rollout is the reason you hear about a problem from the news instead of from your own office.
Workstations: the Thursday after Patch Tuesday, after hours. The cumulative update goes to every managed PC once the first wave of installs looks clean. Reboots are scheduled for early the next morning, before the first shift, so nobody loses work to an "installing updates" screen. Machines need to be on, or plugged in and asleep, Thursday night. Laptops that are off the network pick up the update the next time they connect, and we track the stragglers by name.
Servers: the normal after-hours maintenance window. In a month like this one, domain controllers and any on-premises Exchange server go first, for the LDAP, Active Directory, Windows Search and Exchange fixes above. Servers reboot one at a time, so a file share or a line-of-business application is not down in the middle of an invoice run or a shift change.
Office: its own pass. This is the pass that closes the exploited Outlook flaw. Office updates ship on their own channel, so a machine can be fully current on Windows and still be running vulnerable Outlook. After the pass we verify the installed Office version on each machine instead of trusting the Windows Update checkmark.
Verification, not assumption. After the reboot, our management tools confirm per machine that the update applied, the build number moved, and the machine came back healthy. For the person who looks after your systems, these are the November builds, compiled from IT-Connect and Digital Citizen:
- Windows 11 versions 25H2 and 26H2, and 24H2 Enterprise and Education: KB5132061, builds 26200.9974 and 26300.9974 (and 26100.9974 for 24H2). Windows 11 26H1: KB5132059, build 28000.3501.
- Windows 11 23H2: KB5131087, build 22631.7711. Windows 10 22H2 with ESU: KB5131096, build 19045.7846.
- Windows Server 2025: KB5131080, build 26100.33822. Server 2022: KB5131090, build 20348.5870. Server 2019: KB5131085, build 17763.9487. Server 2016: KB5131291, build 14393.9688.
- Exchange Server Subscription Edition: KB5133453. Office LTSC 2021: 16.0.14334.21048 or later. Office LTSC 2024: 16.0.17932.21140 or later.
What your staff should do now
- Update Office today if nobody has done it for you. In Outlook, File, Office Account, Update Options, Update Now. Restart Outlook when it asks.
- Do not open unexpected message files or Office attachments from outside the company. The exploited flaw needs a file to be opened. If a file arrives from someone you do not know, or from someone you know but did not expect, call them before you open it. The risky attachments post covers which file types to be wary of.
- Use the report button. If you are unsure, report the message instead of opening it. The report-a-phish habit post explains how to set that up.
- If a document asks you to "enable content" or "enable editing," stop and call. That request has been the start of more incidents than any other single click.
- If you already opened something strange, say so immediately. Because the risk here is a captured password hash, the safe response is to change that password and have someone check the account's recent sign-ins. Nobody has ever been in trouble for reporting early.
- Restart when prompted. A Windows fix is not live until the machine reboots.
For whoever manages your IT
Three controls reduce the damage from any password-hash leak, this one included. First, outbound SMB (TCP port 445) to the internet should be blocked at the firewall. The public write-ups do not say which protocol this flaw's outbound connection uses, so treat this as belt and suspenders, but blocking it is the long-standing defense against hash leaks of this kind and costs an ordinary office nothing. The business firewall post covers what a small office firewall should be doing.
Second, long passwords. A hash cracks in proportion to how weak the password behind it is, which is the practical argument for length over forced changes; the password policy post covers the current guidance. Third, multi-factor authentication on Microsoft 365, so a cracked password alone does not open email. Note the limit: MFA protects cloud sign-ins, and it does not stop a hash being replayed against other systems inside the network.
Where this fits
- The October 2026 Patch Tuesday post, the September post, and the August post, for the three previous releases and the patch-cadence habit.
- The clicked-a-phishing-link post, for the first hour after the one click this month's exploited flaw depends on.
- The AI-written phishing post and the security awareness training post, for why the person at the keyboard is still the first layer.
- The EDR versus antivirus post and the managed detection and response page, for catching what a stolen credential does next.
- The patch management post, for the ownership and verification structure that makes a 1,000-fix month routine.
- The managed IT page and the pricing page, for patch management that is verified across every device and what it costs.
We run monthly patch management for small businesses in Monterey County and surrounding areas. This is the kind of thing we watch so you do not have to.
FAQs about the November 2026 Patch Tuesday
How many vulnerabilities did the November 2026 Patch Tuesday fix?
It depends on what you count, which is why the headlines disagree. Microsoft's release notes list 1,094 CVEs for November 10, 2026, and trackers that count differently land between 1,090 and 1,093. One outlet reported as many as 1,235. Of the Microsoft items, 63 are rated Critical, and Microsoft flagged 42 more as more likely to be exploited. It is the second month in a row above 1,000, a little under October's record of more than 1,400. Only one of the flaws is confirmed to be under attack.
What is the Outlook zero-day, and does it affect us?
CVE-2026-124194 is a spoofing flaw in Outlook, rated Moderate with a CVSS score of 6.5. Microsoft marks it as exploitation detected, meaning attackers are already using it. It works when a person opens a crafted file: Outlook connects to a server the attacker controls without showing the usual external-content warning, and that connection can hand over the person's NTLMv2 hash, a scrambled form of their Windows password. An attacker can replay the hash to sign in as that person elsewhere, or crack it to recover the password. Reports say Microsoft does not treat the Preview Pane as an attack vector, so the file has to be opened. Microsoft 365 Apps, Office LTSC 2021 and Office LTSC 2024 are listed as affected, so if your team uses desktop Outlook, assume it applies to you. CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10, 2026, with a federal deadline of November 24.
Does Windows Update fix the Outlook flaw?
No. The fix for this flaw ships through Office, which updates on its own channel, separate from the Windows cumulative update. A PC can show that Windows is fully up to date and still be running a vulnerable Outlook. To check one machine, open Outlook, go to File, Office Account, Update Options, then Update Now. The patched builds are 16.0.14334.21048 for Office LTSC 2021 and 16.0.17932.21140 for Office LTSC 2024. The reports we read do not give a build number for Microsoft 365 Apps, so confirm the update applied rather than comparing numbers. Managed clients do not need to do anything, because we run Office as its own pass and verify the installed version on each machine.
We still run Exchange on-premises. What should happen first?
Three things. First, a Windows Search flaw, CVE-2026-116928, rated 9.8, can be triggered by an email attachment that Exchange indexes automatically, so nobody has to open it. It is fixed in the Windows Server cumulative update, not the Exchange update, so the Exchange server needs both. Second, Exchange Server Subscription Edition has its own update, KB5133453, for CVE-2026-118207, which lets a logged-in attacker with a low-level account run code. Third, the November Windows Server updates also fix the problem that broke Outlook on the web and email sending after October's Windows Server updates. Exchange 2016 and 2019 do not appear in this month's Exchange update list, so if you still run one, ask what is protecting it.
Do we need to do anything about the Entra flaw with the perfect 10 score?
Probably nothing you install. CVE-2026-109469 affects Entra Device Registration, a cloud service Microsoft runs itself, and it is rated CVSS 10.0, which is why it tops any list sorted by score. It is not reported as exploited. The reports we read do not identify a step for customers, and Microsoft's advisory is where any required step would be spelled out, so have your IT provider read it rather than assuming.
When will our machines be patched, and will it interrupt work?
For managed clients, workstations get the monthly update on the Thursday after Patch Tuesday, after hours, with reboots scheduled for early the next morning before the first shift. Leave the computer on, or plugged in and asleep, Thursday night. Servers are patched in their normal after-hours maintenance window. Office updates ship on their own channel, so they go out as a separate pass and we verify the installed version on each machine afterward. Laptops that are off the network catch up the next time they connect, and we track the stragglers. The gap of about 48 hours between release and rollout is deliberate: it lets the first wave of installs surface any bad patch before it reaches your fleet.
Sources: Microsoft Security Update Guide, November 2026 · CISA Known Exploited Vulnerabilities catalog · Dark Reading · Digital Citizen · IT-Connect · SecurityOnline · Qualys
One Outlook flaw is already being used, and Windows Update will not fix it. Is Office current on every machine?
30 minutes with the engineer who runs patching for small businesses in Monterey County and surrounding areas. We'll check whether this month's release (the exploited Outlook flaw, your Office installs, your domain controllers and any on-premises Exchange) has truly applied across your machines, and set up patch management you can prove. No jargon, no obligation.
Book your free assessmentPrefer to talk first? Email sales@ghosxt.com or call (831) 204-0501.