Classic Outlook flaw leaks Windows NTLM hashes: November Office update closes it
A classic Outlook bug, CVE-2026-124194, is being exploited to capture Windows login hashes. Patch through November's Office update, and move off Office 2016 and 2019.

If you run classic Outlook on Windows, treat the November Office update as urgent. Microsoft confirms that CVE-2026-124194 is being exploited in the wild, and it's the only bug in this month's release of more than 1,000 that carries that status. Microsoft rates it Moderate with a CVSS score of 6.5 out of 10, but that rating measures theoretical severity, not active use. Here's who's exposed, how to patch and verify, and why Office 2016 and 2019 users have no fix coming.
Which Outlook is affected
The flaw sits in classic Outlook for Windows, the desktop program that ships with Microsoft 365 and Office. Microsoft's advisory lists Microsoft 365 Apps, Office LTSC 2024 and Office LTSC 2021, in both 32-bit and 64-bit builds. Outlook in Office 2021 and 2024 is affected too.
| Your Outlook | Affected? | What to do |
| Microsoft 365 subscription, classic Outlook (business, Personal or Family) | Yes | Update Office now |
| Office 2024 or Office 2021 (one-time purchase or LTSC) | Yes | Update Office now |
| Office 2019 or Office 2016 | Probably, but support has ended | No fix is coming |
| New Outlook for Windows | Not applicable | Nothing for this bug |
| Outlook on the web, Outlook for Mac, iPhone and Android | Not on Microsoft's list | Nothing for this bug |
One trap for people who've moved to new Outlook: classic Outlook often stays installed alongside it, especially on Microsoft 365 machines. If the classic client is still on the PC, patch it.
Patching and confirming the fix
Microsoft 365 updates itself in the background, but "usually" can stretch to days or weeks. Don't wait on it for this one. Open classic Outlook (Word or Excel works too, since every Office app shares one updater), then go to File, Office Account (File, Account in Word and Excel). Select Update Options, then Update Now. Close Office apps when prompted and let the install finish.
To confirm the result, return to the same page and check the version and build under About Outlook. Compare against the fixed builds below.
| Office version or update channel | Fixed version (build) or later |
| Current Channel (most home and small business subscribers) | 2610 (20527.20196) |
| Monthly Enterprise Channel | 2610 (20527.20194), 2609 (20430.20264) or 2608 (20326.20320) |
| Semi-Annual Enterprise Channel | 2610 (20527.20192), 2609 (20430.20262) or 2608 (20326.20318) |
| Office LTSC 2024 | 2408 (17932.21140) |
| Office LTSC 2021 | 2108 (14334.21048) |
If your build number sits below the row for your channel, the machine is still exposed. Managed fleets should check this through their deployment tooling rather than trusting that updates landed.
Office 2016 and 2019: no fix is coming
Support for Office 2016 and Office 2019 ended on October 14, 2025. Microsoft leaves them off this advisory because it no longer checks or patches them. That's not the same as being safe. Assume their Outlook carries the same weakness, permanently.
This is what end of support looks like in practice: an exploited bug in the wild and no patch on the way. If you still run these versions on machines that handle email, the migration conversation has moved from planning to urgent.
How the flaw works, at a high level
The attack depends on one user action: opening a specially crafted message file, typically delivered as an email attachment. Microsoft hasn't named the file type. Once it's open in classic Outlook, the program reaches out to a network location the attacker controls. Outlook normally warns before fetching outside content, but in this case the warning doesn't appear.
Windows then tries to authenticate to that location using NTLM, an older Microsoft login method, and in doing so sends the user's NTLMv2 hash. That hash is a scrambled form of the password, not the password itself. An attacker holding it can attempt offline cracking, which goes quickly against weak passwords. On a corporate network, the same material can be relayed to other servers that still accept NTLM, which is why the exposure reaches beyond a single mailbox.
Reading a message in the preview pane doesn't trigger it; the attachment has to be opened. That's a thin safeguard, since getting people to open attachments is the core of phishing.
Why "spoofing" undersells it
Microsoft files this under spoofing, which suggests a forged sender address. That's not what happens. The impersonation comes later, when the attacker uses the stolen hash to act as the user. Calling it what it is, this is credential theft, and that's how it should be prioritised.
The Moderate rating reflects the scoring model: user interaction is required, and the bug leaks information rather than running code. Scores describe what a flaw could do, though, and this one is already being used. This month's release also includes 20 Outlook fixes, three rated Critical. None of those Critical bugs is under active exploitation, and this Moderate one is. The same November Office update covers all 20, so one patch cycle handles the lot.
The US Cybersecurity and Infrastructure Security Agency has told federal agencies to apply the fix by November 24, 2026. Private-sector teams don't have a matching deadline, but that date is a sensible internal target.
Not the first Outlook login leak
Outlook has leaked Windows credentials through NTLM before. A 2023 relay issue worked without anyone opening a message at all, and a reminder-sound setting once became another way in. A 2024 NTLM problem raised the same question that's back now: Microsoft's suggestion to block NTLM can cause more disruption than the bug it targets, especially in older line-of-business environments. Plan for that trade-off before someone forces it on you during an incident.
My read: patch classic Outlook this week, verify the build number on a sample of machines, and get a list of any Office 2016 or 2019 installs that still touch email. Those are the machines where the risk stays open after everything else is closed.