
Microsoft's November Patch Tuesday fixed 1,094 vulnerabilities. Sixty-three of them were rated Critical. Four carried the maximum CVSS score of 9.8, including unauthenticated remote code execution in Windows Search and Windows LDAP. And the only flaw in the whole release that attackers are actually using right now is rated Moderate: 6.5.
That is the entire lesson in one number. Severity scores measure how bad a flaw could be. Exploitation tells you what is happening. When the two disagree, believe the exploitation.
What the flaw actually does
CVE-2026-124194 is a spoofing flaw in desktop Outlook, tracked as CWE-356: the product interface does not warn the user of an unsafe action. An attacker sends a specially crafted message file and persuades the target to open it. Outlook then connects to a server the attacker controls without showing the usual warning about external content. In that connection, Windows hands over the user's NTLMv2 hash, which the attacker can use to authenticate as that user, or crack offline to recover the password.
Three details matter for how you triage this:
- Opening the file is required. The Preview Pane is explicitly not an attack vector, per Microsoft. That narrows the exposure to users who open message files from outside the organization, but "open the attachment" is still the oldest trick in phishing, and it still works.
- Only desktop Outlook is affected. Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024, in 32-bit and 64-bit. Outlook on the web, Outlook for Mac, and the mobile apps are not on the affected list.
- Microsoft has not said who is exploiting it. No named actor, no campaign details, no published indicators of compromise. What is confirmed is that exploitation was detected before the patch shipped, the flaw was not publicly disclosed beforehand, and CISA added it to the Known Exploited Vulnerabilities catalog on November 10, with a November 24 remediation deadline for US federal agencies.
Why a 6.5 outranks the 9.8s
A severity-sorted patch list puts CVE-2026-124194 near the bottom, below more than a thousand other fixes. That ordering is wrong for one reason: the 9.8s in this release, including the Windows Search and LDAP remote code execution flaws, have no reported exploitation and no public disclosure. The 6.5 is being used in the wild today.
This is not a flaw in CVSS. The score answers a different question than the one you are asking on patch day. CVSS asks how severe a successful exploit would be, assuming it happens. Your question is which flaw to close first, and the strongest single signal for that is whether anyone is already using it. CISA's KEV catalog exists precisely because of this gap: it is a list of flaws with confirmed exploitation, and it is short on purpose.
The practical rule is simple and survives every Patch Tuesday: exploited first, then internet-facing and unauthenticated, then everything else by severity. A 6.5 with confirmed exploitation goes to the top of the list. A 9.8 with no exploitation goes into the normal rollout.
Check your Outlook build
The fix is the November 2026 Office update. But there is a trap that has caught fleets before: Office updates do not arrive with Windows Update. A machine can be fully patched at the OS level and still run a vulnerable Outlook, because the Office update comes from the Office content delivery network on its own schedule. "We patched Tuesday" is not evidence. The build number is.
1. Find the build on one machine. In Outlook, go to File, then Office Account, and read the version. Or check it from PowerShell, which is the version you want when you have more than a handful of machines:
(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration').VersionToReport
2. Compare it against the fixed build for your channel.
| Product | Fixed build |
|---|---|
| Microsoft 365 Apps, Current Channel | Version 2610 (Build 20527.20196) |
| Microsoft 365 Apps, Monthly Enterprise Channel | Version 2610 (Build 20527.20194), 2609 (20430.20264), or 2608 (20326.20320) |
| Microsoft 365 Apps, Semi-Annual Enterprise Channel | Version 2610 (Build 20527.20192), 2609 (20430.20262), or 2608 (20326.20318) |
| Office LTSC 2024 | 16.0.17932.21140 |
| Office LTSC 2021 | 16.0.14334.21048 |
Microsoft 365 Apps has no single fixed build, because the fix ships per channel. Check the build against your channel, not against a number you saw in a headline.
3. Check the fleet, not the policy. If you manage updates through Intune or Configuration Manager, confirm the installed build on a sample of real endpoints rather than trusting that the update ring deployed. Devices that are offline, deferred by policy, or pinned to an older build stay exposed until they receive one of these builds.
4. If you think a hash already leaked, the patch is not the whole answer. A stolen NTLMv2 hash stays usable until the password changes. If you have reason to believe a user opened a crafted message file, reset that user's password and treat the account as compromised until proven otherwise. Longer term, this is another reason to chip away at NTLM in your environment: enforce SMB signing and extended protection for authentication where you can, and keep pushing the services that still demand NTLM toward Kerberos or modern auth.
A footnote on how it was found
Microsoft credits the discovery to two researchers: one who goes by "nono", and Benoît Sevens, whose acknowledgment reads "using Claude with Anthropic". An AI assistant helped find the flaw that attackers are now using. That is worth noting without turning it into a story about AI saving security. The same tooling that finds flaws for defenders finds them for everyone, and the researchers who report them are still the bottleneck that matters. The disclosure worked the way it is supposed to: privately reported, patched, then published. What failed was not the process. It was the assumption that a Moderate rating means you have time.
You do not have time on an exploited flaw. The score is a guess about impact. Exploitation is a fact about the present. Patch Outlook first, verify the build, and let the 9.8s wait their turn in the normal rollout.
Sources
- CVE-2026-124194 - Microsoft Outlook Spoofing Vulnerability — Microsoft Security Response Center, November 10, 2026
- Exploited Outlook Zero-Day Among 1,094 Flaws Patched by Microsoft — SecurityWeek, November 10, 2026
- Microsoft Patches 1,259 Flaws, Including Exploited Outlook Bug That May Expose NTLMv2 Hashes — The Hacker News, November 11, 2026
- November 2026 Patch Tuesday: 63 Critical Microsoft fixes, plus an Outlook zero day that allows theft of hashed credentials — CSO Online, November 10, 2026
- CVE-2026-124194: Outlook Zero-Day Exposes NTLM Hashes — SOC Prime, November 11, 2026



