# 1,094 flaws in Microsoft software and a zero-day in Outlook

> Microsoft closes November with 1,094 patched vulnerabilities and a zero-day in Outlook that leaks the victim's NTLMv2 hash without opening the preview.
> By José Maldonado · Cybersecurity · 2026-11-12

On November 10, 2026, Microsoft published its monthly updates with 1,094 vulnerabilities fixed, below October's 1,413 but far above what any team can review in an afternoon. The [release breakdown](https://www.securityweek.com/exploited-outlook-zero-day-among-1094-flaws-patched-by-microsoft/) leaves 726 flaws in Windows and 174 in Office. Behind them come 59 in SQL Server, 53 in the company's development tools, 27 in SharePoint Server, 20 in Azure and 9 in Exchange Server.

Among those 1,094 patches there is one that cannot wait. It is CVE-2026-124194, a spoofing flaw in Outlook that Microsoft acknowledges as exploited and that only requires the victim to open a crafted message file. The result ends up being the user's NTLMv2 hash in the attacker's hands, a reusable credential to authenticate as that person on services that trust NTLM. The CVSS score is 6.5 and the severity assigned by the vendor is moderate.

That 6.5 is the uncomfortable part of the bulletin. A flaw with active exploitation and a middling score competes poorly for the attention of a team with a full calendar, and the risk does not depend on the score but on what it exposes: a network credential that serves to move through corporate infrastructure. Anyone administering Office in a company should read the rest of the bulletin after patching this.

## The distribution of November's 1,094 patches

Microsoft's release summary sorts the flaws by family and leaves Windows with two thirds of the total. The table gathers the figures the company publishes and what is worth looking at first in each product block.

Family

Flaws fixed

What weighs most

Windows

726

Critical updates in Windows 10, Windows 11 and Server 2016 to 2025

Office

174

The CVE-2026-124194 zero-day in Outlook

SQL Server

59

Fixes in the database engine and its components

Development tools

53

Components that end up on engineering laptops

SharePoint Server

27

Internal servers with access to corporate documents

Outside the table are the 20 flaws in Azure and the 9 in Exchange Server, plus 165 third-party CVEs that Microsoft republished in its own bulletin and that do not include those in Chrome. October's figure, with 1,413 flaws, is a reminder that the volume record is not broken every month.

The bulletin also closes a chapter for Windows 11 version 23H2, which receives its last monthly updates in the Enterprise and Education editions. Anyone still anchored to that version will stop receiving fixes in December.

## The Outlook zero-day that bypasses the preview

Microsoft's advisory describes an attack without prior authentication. The attacker sends a prepared message file and convinces the victim to open it in an affected version of Outlook; on opening it, the email client connects to a network location controlled by the attacker without showing the usual external content warning. That traffic carries the account's NTLMv2 hash, which is then used to authenticate as the user.

Two technical nuances change the conversation about the risk. The first is that the flaw is not triggered from the preview pane, so the only interaction required is opening the file. The second is that the vulnerability was not disclosed before the patch existed, which leaves no margin for anyone who does not apply the update as soon as it is available.

The affected products are Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024, the three products listed in the advisory. The [NVD entry for CVE-2026-124194](https://nvd.nist.gov/vuln/detail/CVE-2026-124194) dates publication to November 10, 2026 and classifies the flaw as CWE-356, the category of interfaces that do not warn the user of a dangerous action.

The vendor's advisory does not detail the attacks observed or the number of victims, so there is no public way to know whether the flaw is being used against a specific sector or opportunistically.

The only firm clue is the entry itself in CISA's catalog, which places it among the flaws with confirmed exploitation and gives it a longer federal deadline than Barracuda's.

## Why is the hash worth more than initial access?

An NTLMv2 hash is not a plaintext password, but it serves the same purpose on many networks. With that string, an attacker can set up an NTLM relay against services that accept network authentication, or crack the password offline if the hash falls into a known dictionary. The spoofing Microsoft assigns to the CVE describes the first step of the chain, not its final scope.

The scope is always set by the victim's network: a laptop with no outbound restrictions and SMB open turns an opened file into a valid session inside the corporate domain.

For that reason identity audits insist on disabling NTLM wherever possible and requiring SMB signing. Neither of those measures replaces the patch, but they reduce the damage once the hash has already left the organization and the security team can only react. The combination of a middling-score flaw with confirmed exploitation is exactly the scenario in which the monthly patching window arrives too late.

## CISA adds six flaws and sets two deadlines

On the same day, November 10, 2026, CISA added six vulnerabilities to its [catalogue of flaws with real-world exploitation](https://www.cisa.gov/news-events/alerts/2026/11/10/cisa-adds-six-known-exploited-vulnerabilities-catalog). Two affect Barracuda Email Security Gateway: CVE-2026-116606, an authentication bypass rated 9.3, and CVE-2026-111560, a command injection rated 8.6. US federal agencies have until November 13 to close both.

The rest of the batch includes CVE-2026-20320 in Cisco BroadWorks, CVE-2026-111793 in Openwave's Webtop transcoder, Outlook's own CVE-2026-124194 and Chrome's CVE-2026-125350, the eighth [Chrome zero-day in 2026](https://observatorioblockchain.com/en/cybersecurity/chrome-cve-2026-125350-octavo-cero-dia/), which already has its own piece in this outlet. A [roundup of the day](https://www.securitytabs.com/newsdesk/cisa-kev-barracuda-esg-cisco-broadworks-outlook-november-10) confirms the full list and the federal deadlines for each entry.

For Outlook and Chrome the federal deadline is November 24, eleven days after Barracuda's. The gap between one deadline and the other is not arbitrary: it reflects the urgency CISA attributes to each flaw and sets the order in which you should review your own exposure.

That deadline only binds US federal agencies, but security teams elsewhere read it as a gauge of real urgency and as cover with their own management.

## What you should patch first

The sensible sequence starts with Outlook on workstations running Microsoft 365 Apps for Enterprise or Office LTSC 2021 and 2024, continues with machines that receive external mail without aggressive filters, and ends with the rest of the estate. Windows can wait for the monthly window, unless there are servers with RDP or SMB exposed to the internet, where the 726 flaws include critical fixes that should not be left to pile up.

There is also a distribution detail that counts. Some Microsoft fixes arrive only through the Microsoft Store and not through Windows Update, as happened with [the Paint flaw CVE-2026-83844](https://observatorioblockchain.com/en/technology/paint-cve-2026-83844-parche-microsoft-store/), so a policy that only looks at the monthly cycle leaves gaps. It is worth cross-checking the inventory against the store catalogue before declaring the month closed.

The same logic applies to edge devices. The [SonicWall flaw CVE-2026-19868](https://observatorioblockchain.com/en/cybersecurity/sonicwall-cve-2026-19868-vpn-saml-mfa/), which allowed VPN access without passing MFA, remains the reminder that exposed appliances get patched off-schedule and that the CISA catalogue works as a priority list, not as an administrative formality.

## What the volume says about the patch cycle

A bulletin of 1,094 flaws is not read, it is filtered. The figure mixes 165 republished third-party CVEs with entire families of bugs that no organization will ever see exploited, while the flaw that matters this week is a 6.5 that hands over a credential and needs nothing more than a double click. Volume measures the health of a vendor's development process; priority is set by active exploitation and the KEV catalogue deadline, which this time gives two weeks to the Outlook flaw and three days to the Barracuda one, counted from the bulletin's publication.

Microsoft has fixed more than 5,000 vulnerabilities in 2026. On that schedule, the only sustainable defence is a decent inventory and a patching order written before the bulletin arrives, because the alternative is trusting that no one opens the wrong file.
