Microsoft's November Patch Tuesday landed on 10 November with somewhere around 1,100 fixes, depending on whose count you trust. Only one of them is marked as already being exploited, and it's in Outlook. It lets an attacker grab a user's password hash just by getting them to open a file.
Outlook is on almost every office PC, so this post is the short, practical version: what the bug does, how to make sure Outlook and Windows are actually patched, and two network settings that stop this whole class of attack, not just this one bug.
Quick answer
CVE-2026-124194 is an Outlook spoofing bug fixed in the November 2026 Patch Tuesday and already exploited. Opening a crafted file can make Outlook connect to an attacker's server without the usual external-content warning, leaking the user's NTLMv2 password hash. Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024 are affected. Fix it by updating Office (File > Office Account > Update Options > Update Now) and installing the November Windows update. To block this kind of leak generally, stop outbound TCP 445 to the internet at your firewall.
What the Outlook bug actually does
Microsoft lists CVE-2026-124194 as a spoofing vulnerability rated Moderate, CVSS 6.5. The rating sounds mild, but the result isn't. According to Qualys' Patch Tuesday review, a specially crafted file can make Outlook connect to a network location the attacker controls "without displaying the usual external-content warning".
When Windows connects to a file share, it tries to sign in automatically with NTLM, sending a hash of the user's password. CSO Online explains what an attacker can do with that NTLMv2 hash: relay it to other systems to sign in as the user, or try to crack it offline to recover the actual password. Weak passwords fall quickly.
Two things make it urgent. It's already being exploited, and CISA has added it to its Known Exploited Vulnerabilities catalog with a fix-by date of 24 November 2026 for US federal agencies. That date is a decent deadline for everyone else too.
What else is in November's Patch Tuesday
| CVE | What it is | Why it matters |
|---|---|---|
| CVE-2026-124194 | Outlook spoofing, leaks NTLM hashes | Exploited in the wild. Needs the user to open a file |
| CVE-2026-116928 | Windows Search remote code execution, CVSS 9.8 | Critical and network-reachable. Not known to be exploited yet |
The total count varies by source, from about 1,094 to 1,235 fixes, mostly because some reports include Edge and other products. You don't need the exact number. You need both Office and Windows updated.
Step 1: Update Office and Outlook
Office updates separately from Windows, which is exactly why it gets missed. In Outlook (or Word, Excel, any Office app):
- Click File > Office Account (in Outlook it may say Office Account or just Account).
- Click Update Options > Update Now.
- Close Office apps when asked, and let it finish.
On the same page, About Outlook shows your version and build. If Update Options is missing or greyed out, your organisation manages Office updates centrally. Ask IT to confirm the November update is out to your channel.
For admins who'd rather script it, the Click-to-Run updater can be triggered from an admin prompt:
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user
Step 2: Install the November Windows update
Open Settings > Windows Update, click Check for updates and install everything, then restart. On Windows 11 the November cumulative update is KB5132061. After it, winver shows build 26100.9974 (24H2), 26200.9974 (25H2) or 26300.9974 (26H2). On Windows 10, this needs the PC to be enrolled in Extended Security Updates, otherwise it gets nothing.
Step 3: Stop NTLM hashes leaving your network
This is the part that outlasts this one bug. Outlook NTLM leaks have happened before: in 2023, CVE-2023-23397 worked in a similar way, and Microsoft's advice back then included two network-level protections. They still apply.
Block outbound SMB (TCP 445) to the internet
The hash leak works because the PC reaches out to the attacker's server over SMB, which is TCP port 445. There's almost never a good reason for an office PC to talk SMB to the internet. Block outbound TCP 445 on your router or firewall, from your LAN to any outside address. On a FortiGate that's a simple deny policy from the internal interface to WAN for the SMB service, placed above your general internet policy.
If you can't change the firewall, Windows Firewall can do it per PC. This rule blocks SMB to internet addresses only, so local file shares keep working:
New-NetFirewallRule -DisplayName "Block outbound SMB to internet" -Direction Outbound -Protocol TCP -RemotePort 445 -RemoteAddress Internet -Action Block
Test it afterwards by opening a shared folder on your own network. If that still works, you're fine.
Put admin accounts in Protected Users
On an Active Directory domain, members of the Protected Users group can't use NTLM authentication at all. Put your domain admins and other high-value accounts in it. Test with one account first, because anything that relies on NTLM for that account will stop working, which is the point, but it's better to find out on a Tuesday afternoon than a Friday night.
What can go wrong
- Office "up to date" but on an old build. Some organisations use the Semi-Annual Enterprise Channel, which gets security fixes on a different schedule. Check the build number against Microsoft's update history for your channel rather than trusting the message.
- Blocking 445 broke something. If a cloud file service or a remote branch genuinely uses SMB over the internet, it'll stop. That's rare and usually better handled over a VPN anyway.
- Users still open odd attachments. The patch fixes this bug. Training and a mail gateway that strips risky attachments deal with the next one.
Rolling back
If the Office update breaks something, you can uninstall the Windows update from Settings > Windows Update > Update history > Uninstall updates, but think hard before rolling back a patch for an exploited bug. For the firewall rule, removing it is one line:
Remove-NetFirewallRule -DisplayName "Block outbound SMB to internet"
A few things I learned
- Office patching is a separate job. A fully updated Windows PC can still be running vulnerable Outlook.
- Don't judge by CVSS alone. A 6.5 that's being exploited beats a 9.8 that isn't, in terms of what to patch first.
- Blocking outbound 445 is cheap. It's one firewall rule and it shuts a door that keeps getting used.
I've written more about Outlook in fixing common Outlook 365 problems and managing Outlook storage, and about last week's Microsoft 365 outage. For the firewall side, my Fortinet network standard post shows how I structure office firewall policies. If you'd like someone to check your office for this, that's part of my IT services.
Frequently asked questions
What is CVE-2026-124194?
It is an Outlook spoofing vulnerability fixed in Microsoft's November 2026 Patch Tuesday and already exploited. A crafted file can make Outlook connect to an attacker's server without the usual warning, leaking the user's NTLMv2 password hash.
How do I update Outlook to fix the zero-day?
In Outlook, go to File, Office Account, Update Options and click Update Now, then restart Office. Also install the November Windows update. If Update Options is missing, your organisation manages Office updates, so ask IT to confirm the November fix is deployed.
Which Office versions are affected by CVE-2026-124194?
Reports list Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024. Anyone using classic Outlook should install the latest Office update regardless of edition, because it is being exploited.
Does blocking port 445 stop NTLM hash theft?
It stops the common version of it. The leak usually works by the PC connecting to an attacker's server over SMB on TCP 445. Blocking outbound 445 to the internet at your firewall prevents that, while local file shares keep working.
What is the Windows update for November 2026?
On Windows 11 it is KB5132061, released on 10 November 2026. After installing it, the build is 26100.9974 on 24H2, 26200.9974 on 25H2 and 26300.9974 on 26H2. Windows 10 PCs need Extended Security Updates to receive it.
