
On Tuesday, November 10, 2026, Microsoft’s monthly update fixed CVE-2026-124194 in Outlook, a flaw Microsoft itself says it detected being exploited. It tends to get lost behind headlines about “more than 1,000 fixes,” but it was the only flaw in use in the wild this month. This article reflects information as of November 15, 2026.
Microsoft’s advisory (the MSRC page) calls it “Microsoft Outlook Spoofing Vulnerability.” An attacker sends a specially crafted message file and convinces the recipient to open it. When it is opened, Outlook connects to an attacker-controlled network location without showing the usual external-content warning, and the user’s authentication information can be disclosed to the attacker.
What leaks is the user’s NTLMv2 hash. Microsoft’s FAQ says the attacker could use it to authenticate as that user. The weakness class is CWE-356, a product UI that does not warn the user of unsafe actions.
Reported counts for the November update vary. The Hacker News says 1,259, of which 165 carry identifiers issued by parties other than Microsoft (The Hacker News). Other outlets give figures from 1,093 to 1,235, so the counting method evidently differs. This article doesn’t use a count.
Instead, I went through every entry in the November monthly-update data MSRC publishes (CVRF) programmatically. Exactly one is marked “Exploited: Yes,” CVE-2026-124194. None is marked “Publicly Disclosed: Yes.”
Microsoft rates it Moderate, with a CVSS score of 6.5. In MSRC’s data, the score adjusted for exploitation status is 6.2. It is not rated Important or Critical, because only information is exposed, nothing is altered or taken down, and the user has to open the file.
But the fact that it is being exploited barely registers in that number. On November 10, CISA added it to its Known Exploited Vulnerabilities (KEV) catalog and set a federal remediation deadline of November 24. Use in ransomware campaigns is listed as “Unknown” (CISA data, checked directly by me on November 15). This is not a flaw to put off because of a middling score. Putting actively exploited flaws first is the same priority I described in what to patch first among the 16 fixes in Node.js’s November security release, which includes the already exploited Brotli flaw.
Microsoft’s FAQ states plainly that the Preview Pane is not an attack vector for this flaw. Receiving the email, or viewing it in the preview, does not trigger it. The user has to open the crafted file the attacker sent. Another FAQ entry puts it as convincing the user to open a malicious Office file.
Some commentary reportedly suggests it can fire from the preview too, but I couldn’t confirm any basis for that. The official statement is as above.
NTLM is an authentication mechanism Windows has used for a long time, and NTLMv2 is its newer version. The hash that leaks is not the password itself. Still, SOC Prime, relaying BleepingComputer’s reporting, says a captured hash may be subjected to offline password cracking (SOC Prime). Whether it can be cracked depends on how strong the password is.
MSRC lists Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024, in both 32-bit and 64-bit editions. The fixed builds are 16.0.14334.21048 or later for LTSC 2021 and 16.0.17932.21140 or later for LTSC 2024. Microsoft 365 Apps builds differ by update channel; the November 10 Current Channel build is Version 2610 (Build 20527.20196) (Microsoft’s update history).
Office 2019, the new Outlook and Outlook for Mac do not appear in MSRC’s list of affected products. However, MSRC’s list names only “Microsoft 365 Apps for Enterprise,” and I couldn’t confirm how other plans used by smaller companies are treated. The surest way to know whether your build is fixed is to check it directly, as described under “What to do now.”
Microsoft hasn’t said who is using it, at what scale, since when, or against whom. SOC Prime writes that no indicators of compromise, such as IP addresses, have been published, and that no public exploit code exists, though that is not a primary source either.
Also, MSRC credits the discoverers as “nono” and “Benoit Sevens using Claude with Anthropic” (the acknowledgments field of MSRC’s monthly update data).
First, check whether your own Office is fixed. In Outlook, open File, then Office Account, and look at the version and build under About Outlook. If it is older than the fixed builds above, choose Update Options on the same screen and then Update Now. If an administrator or a maintenance company handles updates for your company’s PCs, ask whether the November 10 update has reached everyone’s machine.
This flaw depends on getting a user to open a file. Don’t open files from senders you don’t recognize, including attached Office files. If you think you opened one, tell your administrator or maintenance company right away and change your password. Telling staff those two things is worth about as much as the update itself.
Administrators have one more step: block SMB traffic (TCP port 445) from the company network to the internet. In general, this kind of credential leak happens over SMB traffic, so blocking it closes the destination. Whether this particular flaw actually uses SMB can’t be confirmed from Microsoft’s description. MSRC’s page lists no workaround; this measure is one SOC Prime presents as Microsoft’s recommendation, which I couldn’t confirm in a primary source. Companies that use SMB for file sharing outside the network should check the impact first.
How to run updates, and who does what, is covered in how to keep your software updated, from our website security basics series. The WordPress core flaw from the same period is covered in the WordPress core flaw that hits you mid-update.
We are currently taking free consultations on security. Questions like "Is our site safe?" or "Where should we start checking?" are welcome.
