Microsoft’s November 2026 security update marks one vulnerability as exploited in the wild: CVE-2026-124194, an Outlook spoofing flaw that can hand an attacker a user’s NTLMv2 hash. Microsoft rates it Moderate, with a CVSS score of 6.5, which puts the month’s only confirmed attack below 1,093 of Microsoft’s own fixes on a severity-sorted list.
What Microsoft disclosed about the Outlook flaw
Microsoft describes CVE-2026-124194 as a case where Outlook “does not warn user of unsafe actions”. According to the FAQ in its advisory, an unauthenticated attacker sends a specially crafted message file and convinces a user to open it in an affected version of Outlook. Opening the file can make Outlook connect to an attacker-controlled network location without the usual external-content warning. The advisory states the consequence plainly: “This vulnerability discloses a user’s NTLMv2 hash to the attacker who could use this to authenticate as the user.”
Three details from the advisory shape the response. The Preview Pane is not an attack vector, so a user has to open the file. Microsoft marks “Customer Action Required” as Yes, and points to the Microsoft 365 Apps security update channel for the fix. The advisory credits two finders: Benoît Sevens, listed as using Claude with Anthropic, and a researcher listed as nono. Microsoft’s data marks the flaw as exploited and not publicly disclosed before release, and the advisory does not say who used it or against whom.
How big the release is, and why the counts differ
Security vendors published different totals for the same release on 10 November. Cisco Talos counted 1,095 vulnerabilities, Tenable 1,093 and CrowdStrike 1,252. Microsoft’s own machine-readable release file, the November 2026 CVRF document, explains most of the spread. It lists 1,362 CVE entries, but only 1,095 of them name Microsoft as the assigning authority. The rest are third-party CVEs that Microsoft tracks because it ships the affected code: 165 assigned by Chrome, 41 by Linux, and smaller groups from CPANSec, VulnCheck and Red Hat.
Within Microsoft’s 1,095, the file rates 64 Critical, 1,029 Important and 2 Moderate. The exploited Outlook flaw is one of the two Moderate entries. We made the case last month that the CVE count should not set your priorities, and November repeats the pattern with a different twist: the count is large, and the one flaw with confirmed use sits near the bottom of the severity scale.
The flaws Microsoft expects attackers to try next
Microsoft flags 42 of its own CVEs as “Exploitation More Likely”. Most are Windows elevation-of-privilege bugs in components such as the kernel, Installer, Print Spooler and graphics kernel. A handful are remote code execution flaws that touch servers most enterprises run. Talos lists their CVSS scores:
- CVE-2026-118207, Microsoft Exchange Server remote code execution, CVSS 8.8.
- CVE-2026-118146, Active Directory Domain Services remote code execution, CVSS 8.8, and CVE-2026-118148, an Active Directory Domain Services elevation of privilege flaw, CVSS 7.5.
- CVE-2026-113862, Windows Network Address Translation (NAT) remote code execution, CVSS 8.1.
- CVE-2026-119952, Windows Schannel remote code execution, CVSS 8.1.
Exchange servers were also the target of the Turla tooling ESET described when it tied Cereal malware to Exchange servers. A remote code execution flaw on that list belongs in the same week as the Outlook fix.
Why a Moderate rating can sit on the exploited flaw
A severity rating scores what a single flaw does on its own. CVE-2026-124194 needs a user to open a file and yields a credential hash, so on paper it is a spoofing bug with no code execution. The exploitation flag reports something different: that attackers are using it. An NTLMv2 hash that lets someone authenticate as the user is an identity compromise, and its reach depends on what that user’s account can touch.
In our reading, that gap is the main operational lesson of this release. A patch process that sorts by severity alone would queue the Outlook fix behind more than a thousand Important and Critical items, several of which Microsoft itself considers less likely to be exploited. Teams that already start the clock on release day, as we argued in our case for a release-day patch clock, should add a second rule: an exploited flag outranks a severity label.
What it means for the security leader
The Outlook fix arrives through the Microsoft 365 Apps update channels, which many organisations roll out in stages over days or weeks. That staging is the exposure window, and it applies to the one flaw this month that attackers are known to be using. Desktop teams need to know which update channel each user population is on and how quickly the November build reaches it.
The credential angle also widens the response beyond patching. A disclosed NTLMv2 hash is useful to an attacker wherever NTLM authentication is still accepted, so identity teams have a stake in this release as much as desktop teams do. Their question is narrower than the patch queue: which accounts receive outside mail and still authenticate with NTLM anywhere in the estate, and what those accounts can reach.
What to do this week
- Push the November Microsoft 365 Apps security update to every Outlook installation and confirm it on a sample of endpoints in each update channel.
- Check whether workstations can send authentication traffic to hosts on the internet, and close that path where business needs allow.
- Review sign-in logs for NTLM authentication from unfamiliar hosts against accounts of users who receive external mail, starting with privileged staff.
- Schedule the Exchange Server and Active Directory Domain Services fixes listed above in the same cycle, and test domain controllers first in a staging ring.
- Remind staff that opening an unexpected message file from outside the organisation is the step this attack needs.
Source: Microsoft Security Response Center, CVE-2026-124194 Microsoft Outlook Spoofing Vulnerability