Outlook Zero-Day CVE-2026-124194: The MSP Patch Plan for November 2026

Microsoft's November 10 Patch Tuesday fixed CVE-2026-124194, a classic Outlook flaw that attackers were already using. A user opens a crafted message file, Outlook quietly connects to the attacker's server without the usual external-content warning, and the user's NTLMv2 hash goes with it. CISA added it to the Known Exploited Vulnerabilities catalog the same day and gave federal agencies until November 24.
Microsoft's advisory scores it 6.5 and rates it Moderate. Don't let that sort it to the bottom of the queue. "Exploited: Yes" beats a CVSS number every time.
Quick answer: MSPs should confirm every classic Outlook install across clients is on the November 10 Office build this week, then find the machines that can't take the fix. Office 2016 and 2019 left support on October 14, 2025, so those seats need an upgrade project, quoted per machine. Blocking outbound SMB and reviewing Protected Users is cheap hardening worth adding to the same quote.
What the flaw actually does
The attack needs two things: a malicious file in the user's hands and the user opening it. Microsoft's FAQ says the Preview Pane is not an attack vector, so a user who never opens the attachment isn't hit by this one.
Once it's open, the damage is the hash. Microsoft's advisory says the attacker gets the user's NTLMv2 hash and could use it to authenticate as that user. For a regular user that means their mailbox and file shares. For the office manager who still has local admin on half the machines, it's a lot worse.
That's why this lands on an MSP's desk and not just Microsoft's. The patch is free. Finding the machines that can't take it, and the accounts that make a stolen hash expensive, is the actual work.
Turn the stragglers into one approved project
Scopable pulls the client environment into the scope, so every machine still on Office 2016 or 2019 becomes a line with its license and labor on a quote the client approves. Start for free and run it on your first client today.
Who is exposed
Microsoft's advisory lists six affected products: Microsoft 365 Apps for enterprise and Office LTSC 2021 and 2024, each in 32-bit and 64-bit. New Outlook for Windows, Outlook on the web, and Outlook for Mac aren't on that list.
The fix ships in the Office update, not the Windows cumulative update. If your patch policy only watches Windows, check it. Microsoft's Office security update release notes list the November 10 builds:
| Edition and channel | Fixed build |
|---|---|
| Microsoft 365 Apps, Current Channel | Version 2610, build 20527.20196 |
| Microsoft 365 Apps, Monthly Enterprise Channel | 2610: 20527.20194, 2609: 20430.20264, 2608: 20326.20320 |
| Microsoft 365 Apps, Semi-Annual Enterprise Channel | 2610: 20527.20192, 2609: 20430.20262, 2608: 20326.20318 |
| Office LTSC 2024 | Version 2408, build 17932.21140 |
| Office LTSC 2021 | Version 2108, build 14334.21048 |
Pull the installed Office build from the RMM for every client and compare it to that table. Anything older than the build for its channel is unpatched, whatever the update policy says.
The machines that won't get a fix
Office 2016 and 2019 aren't in the affected list because they aren't supported. Microsoft's end of support page says support ended October 14, 2025 and security fixes may no longer ship. A client running classic Outlook from a 2019 perpetual license has no patch coming. Treat those seats as exposed.
Same goes for Microsoft 365 Apps stuck on a channel version that's out of service. Microsoft's update history shows which versions still get builds. If a machine is pinned to something older, find out who pinned it and why.
Hardening that makes the next one cheaper
The patch closes this hole. Outlook has leaked NTLM hashes before, though, and it will again. Two changes make a stolen hash worth less, and both fit inside a few hours per client.
- Block outbound SMB at the firewall: TCP 445 to the internet has almost no legitimate use at an SMB client. Blocking it cuts the SMB path for hash leaks like this one. It doesn't stop WebDAV over HTTP, so it's a backstop, not the fix.
- Put admin accounts in Protected Users: members of the Protected Users group can't authenticate with NTLM, so a leaked hash for those accounts is far less useful. Test first. Service accounts and some older apps break when NTLM goes away.
While you're in there, check who has local admin rights and why. A stolen hash from a standard user is a mailbox problem. A stolen hash from an admin is an incident.
The rest of November worth same-day attention
CVE-2026-124194 is the only exploited flaw in Microsoft's November release. Three others are rated Critical and "Exploitation More Likely" in Microsoft's Security Update Guide, and they're the next ones to push:
- CVE-2026-118146: remote code execution in Active Directory Domain Services. An authenticated attacker with low-level access can run code on the server. Patch the domain controllers.
- CVE-2026-118207: remote code execution in Exchange Server, same low-level authenticated access. If a client still runs an on-prem or hybrid Exchange box, it goes on the list.
- CVE-2026-119952: unauthenticated remote code execution in Windows Schannel through a crafted packet. Microsoft rates the attack complexity high, but it needs no login and no user.
Two non-Microsoft entries hit the KEV catalog the same week. CISA added a chained pair of Barracuda Email Security Gateway flaws (CVE-2026-116606 and CVE-2026-111560) on November 10, and a Check Point Gaia OS flaw (CVE-2026-123039) on November 13. If any client still runs a Barracuda ESG appliance or a Check Point gateway, check it today. The Barracuda Email Protection vs Defender for Office 365 comparison is a decent starting point if the ESG conversation turns into a replacement conversation.
How to scope and quote it
Pushing the November Office build to supported Microsoft 365 Apps installs is managed patching. It's what the client already pays for, so don't quote it.
The stragglers are a project. Build it from the inventory, one line per machine:
| Line | What it covers |
|---|---|
| Office upgrade, per machine | Move Office 2016 or 2019 to Microsoft 365 Apps, including profile, add-in, and macro checks. |
| Licensing | Microsoft 365 Apps or a plan that includes it, through CSP, if the client doesn't already own it. |
| Hardening | Outbound SMB block, Protected Users review, local admin cleanup. |
| Exceptions | Any machine that can't move yet, with the reason, the owner, and a date. |
The add-ins are where the hours hide. The 2014 Excel macro the billing team runs payroll on. The PDF printer plugin nobody remembers buying. Ask before you quote, not after the upgrade breaks them. The MSP project scoping guide has the hour categories most teams forget.
If you're building that inventory from RMM exports and a spreadsheet, Scopable's assessment and scoping software pulls the client environment into the scope so the version list, the gaps, and the project lines come from the same data. You did a version of this last week for Windows Server 2016 end of support, and the June 2026 Patch Tuesday priority plan has the triage buckets if you want one rule for every month.
What to send clients this week
Keep it short. Tell each client the Outlook fix is in, how many of their machines got it, and how many can't take it. For the second number, attach the quote.
Microsoft fixed an Outlook flaw on November 10 that attackers are already using to steal sign-in credentials. Your supported machines are patched. Four machines still run Office 2019, which Microsoft stopped fixing last October, so they stay exposed until we upgrade them. The quote for that is attached.
A client who sees "four machines, exposed, here's the fix" approves faster than one who gets a CVE number.
Frequently Asked Questions
What is CVE-2026-124194?
CVE-2026-124194 is a spoofing flaw in classic Outlook that Microsoft fixed on November 10, 2026 and flagged as exploited in the wild. A crafted message file, once a user opens it, makes Outlook connect to an attacker's server without the usual external-content warning, which leaks the user's NTLMv2 hash. Microsoft says the Preview Pane is not an attack vector. CISA added it to its Known Exploited Vulnerabilities catalog on November 10.
Which Outlook versions does CVE-2026-124194 affect?
Microsoft lists Microsoft 365 Apps for enterprise and Office LTSC 2021 and 2024, 32-bit and 64-bit. The fixed builds are Current Channel 20527.20196, Monthly Enterprise Channel 20527.20194, Office LTSC 2024 16.0.17932.21140, and Office LTSC 2021 16.0.14334.21048. Office 2016 and 2019 left support on October 14, 2025 and don't get security fixes, so treat them as exposed and plan the upgrade.
How should an MSP quote the Outlook CVE-2026-124194 remediation?
Patching supported Microsoft 365 Apps is normal managed patching. Quote the rest as a project: one line per machine still on Office 2016, 2019, or an unsupported build, with the license and the upgrade labor, plus a short hardening line for blocking outbound SMB and reviewing which admin accounts belong in Protected Users.


