Out of everything Microsoft fixed this month, exactly one flaw is being exploited in the wild right now. It lives in Outlook, and it was in use before the patch existed.
The flaw is tracked as CVE-2026-124194. Microsoft calls it an Outlook spoofing vulnerability, which is the kind of label that makes people scroll past. Read the actual description and it looks a lot more serious than that.
What actually happens when someone opens the file
An unauthenticated attacker sends a specially crafted message file and convinces someone to open it. Opening it causes Outlook to reach out to a network location the attacker controls. The part that matters: Outlook does not show its usual external-content warning first.
While that connection happens, Windows tries to authenticate to the remote share and hands over the user's NTLMv2 hash in the process. The attacker captures it. From there it becomes an offline cracking problem, and weak or reused passwords fall fast.
Picture the realistic version of this in a small business. A message arrives that looks like an invoice, a delivery note, or a shared document from a supplier. Someone in accounts opens it because that is literally their job. Nothing visibly bad happens. No ransomware, no popup, no locked screen. Just a quiet outbound connection and a credential leaving the building.
Nothing visibly bad happens. That is exactly what makes it work.
There is one small mercy worth knowing. The Preview Pane is not an attack vector for this flaw, so someone has to actually open the file, not just glance at it in the reading pane.
Why "spoofing" undersells this
Microsoft rates it Moderate with a CVSS score of 6.5. That number is technically defensible and practically misleading. The score accounts for the user having to open something, and it treats the impact as information disclosure rather than account takeover.
In the real world, a stolen NTLMv2 hash gets cracked offline or relayed, and the result is someone logging in as your employee. Severity labels describe the technical mechanism, not the business outcome.
That matters because of what happens next. Reused passwords mean one stolen hash can reach well beyond email. If that person is an admin, or uses the same credentials for your finance portal or line-of-business app, the scope quietly widens.
The affected products are the ones most businesses actually run: Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024. Check Microsoft's advisory for the exact builds rather than assuming your version is covered.
CISA added it to its Known Exploited Vulnerabilities catalog on 10 November and gave federal agencies until 24 November to remediate. That two-week window is not bureaucratic housekeeping. It is CISA's estimate of how long this should be allowed to stay open.
The same round brought Microsoft past 5,100 patches for the year, which is the context for why nobody can eyeball this list anymore.
What to do today, in order
- Update Office, not just Windows. The fix ships through Office updates, not the Windows cumulative update, so a fully patched Windows machine can still be running a vulnerable Outlook. Office LTSC 2021 needs build 16.0.14334.21048 or later, and Office LTSC 2024 needs 16.0.17932.21140 or later. Microsoft 365 Apps for Enterprise needs the current security release on your servicing channel.
- Reset credentials for anyone who opened a suspicious attachment in the last two weeks. If you cannot rule out exposure, treat the account as compromised instead of waiting for proof.
- Check for password reuse between Microsoft accounts and everything else. The hash is only as dangerous as the number of doors that password opens.
- Block outbound SMB to the internet and restrict outbound NTLM authentication at your network edge. Outbound NTLM is what makes this class of attack profitable. It is a bigger project than a patch, but it removes the payoff.
The patch itself is not going smoothly
Worth knowing before you start, because this month's updates are carrying baggage. Microsoft has confirmed that the November Windows 11 updates fail to install on some systems that took the October preview update, with 0x80070306, 0x800f0989, and 0x800f0993 errors.
It has also acknowledged activation and licensing failures with 0x80041008 codes after these updates, and a printing bug that breaks documents containing images with zero height or width. SQL Server performance and stability issues have been reported from updates going back to October.
None of that is a reason to skip patching. It is a reason to test on one machine, keep your rollback plan within reach, and not schedule this for Friday afternoon.
One more thing to keep straight: the Microsoft 365 outage that took Outlook down worldwide on 12 November is a separate event. Microsoft said there was no indication of malicious activity behind it. Do not let the two stories blur into one.
If you are not sure whether your Outlook clients are on a patched build, or whether any credentials have already walked out the door, that is a fifteen-minute question with a clear answer.
Book a 15-minute check on your Microsoft 365 exposure
We will tell you what we find and what to fix first. No pitch, no obligation.