For the second month in a row, Microsoft's Patch Tuesday has passed four digits. The November 10 release lists 1,094 CVEs in Microsoft's security update guide, according to CyberScoop: 726 in Windows and 174 in Office. That follows October's release, which CyberScoop counted at 1,413 defects. The Record reports that 63 of this month's vulnerabilities are rated critical. It also cites Tenable's Satnam Narang, who says Microsoft has now disclosed more than 5,160 vulnerabilities this year.
For a patch team, the headline number is a workload problem, not a crisis. Out of more than a thousand entries, Microsoft and outside researchers point to one flaw that attackers are already using. None of the 1,094 was publicly known before the release, according to The Register, so for nearly all of them, defenders get the fix before anyone outside Microsoft has the details.
The one being exploited: CVE-2026-124194 in Outlook
The exploited bug is CVE-2026-124194, which Microsoft classifies as an Outlook spoofing vulnerability. Its CVSS 3.1 base score is 6.5, rated Medium. The NVD record describes the weakness as Outlook's interface not warning the user about an unsafe action. CISA's catalog names it "Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability" and lists the weakness as CWE-356.
The score metrics explain both the risk and the low number. The attack works over a network, needs no privileges and is not complex to pull off. The one thing it needs is user interaction: the victim has to open something. The metrics rate the impact on confidentiality as high, meaning information leaks out. They don't rate any impact on integrity or availability.
Here is what happens. A specially crafted message file makes Outlook connect to a location the attacker controls, and Outlook skips the warning it normally shows before loading external content. That connection hands over authentication material.
The Zero Day Initiative's Dustin Childs is blunter about how serious that is. The Register quotes him as saying the bug is labeled spoofing but "the impact is bigger than the name suggests," because the flaw discloses the user's NTLMv2 hash. NTLM is an older Windows authentication protocol. Its hashes are not passwords, but attackers value them: they can try to crack them offline, or relay them to log in elsewhere as the victim. A bug that quietly sends those hashes to an attacker's server is a credential-theft bug, whatever its official category.
Microsoft has not said when the attacks started or who is behind them, The Register reports. No source attributes the activity to a particular group. The Record reports that Microsoft said the flaw was discovered by Benoît Sevens using Anthropic's Claude.
CISA added CVE-2026-124194 to its Known Exploited Vulnerabilities (KEV) catalog on November 10. Federal civilian agencies have until November 24 to fix it. The catalog lists ransomware use as "Unknown," and its required-action text cites CISA Binding Operational Directive 26-04. In the NVD record, CISA's SSVC assessment, a framework the agency uses to rank which vulnerabilities to act on first, also marks exploitation as active.
Other bugs worth moving up the list
Being exploited makes the Outlook bug the most urgent, but it isn't the worst bug in the release. CyberScoop highlights two others:
- CVE-2026-116928, Windows Search. Attackers can reach this flaw through Exchange Server. ZDI's Childs describes it as zero-click code execution: no one has to open or click anything. Organizations running Exchange Server should treat it as urgent even though it is not known to be exploited.
- A Windows LDAP flaw rated CVSS 9.8. The Register identifies it as CVE-2026-119958. LDAP is the directory protocol behind Active Directory lookups, and Childs says the flaw could be "quite destructive, especially on Domain Controllers." A 9.8 score usually means the bug can be exploited remotely without authentication.
Same-day KEV additions with shorter deadlines
Microsoft wasn't the only vendor added to KEV on November 10. CISA also added two Barracuda vulnerabilities, CVE-2026-116606 and CVE-2026-111560, with a due date of November 13, only three days later. The catalog marks both for forensic triage, and The Record reports that CISA told agencies to patch them by Friday and to investigate whether they had already been compromised. In practice, that means patching alone may not be enough: if a vulnerable Barracuda appliance was exposed, assume it may already have been breached and check it.
CISA also added Cisco BroadWorks CVE-2026-20320, due November 24, the same deadline as the Outlook bug.
N-able takes hosted N-central offline
Separately, The Record reports that N-able took its hosted N-central environments offline after a researcher uncovered more than 30 serious flaws and proof-of-concept code was published. N-central is remote monitoring and management software used by managed service providers. According to The Record, N-able says it is seeing scanning activity tied to the published code but has no evidence that any customer environment has been successfully exploited. ZeroDayFeed has not independently verified those details. MSPs and their customers should watch N-able's own advisories for restoration and patch guidance.
What It Means for Defenders
Who is affected by the Outlook zero-day: According to NVD, CVE-2026-124194 affects Microsoft 365 Apps, Office LTSC 2021 and Office LTSC 2024. Any organization whose staff read mail in desktop Outlook from those products is in scope.
What to patch, in order:
- Barracuda CVE-2026-116606 and CVE-2026-111560: the November 13 deadline is the tightest in this batch. Patch them, and follow CISA's direction to look for signs of compromise.
- Outlook CVE-2026-124194: NVD lists the fixed builds as 16.0.14334.21048 for Office LTSC 2021 and 16.0.17932.21140 for Office LTSC 2024. Make sure Microsoft 365 Apps clients have taken the November update. Check the build numbers your endpoints actually report, not just whether the patch was deployed. The federal deadline is November 24.
- Cisco BroadWorks CVE-2026-20320: also due November 24 for federal agencies.
- Windows Search CVE-2026-116928 and the 9.8-rated LDAP flaw: put these early in your Windows rollout, especially on Exchange servers and domain controllers.
What to check and rotate: The Outlook bug leaks NTLMv2 hashes rather than running code, so patching closes the hole but doesn't undo any theft that already happened. If you have reason to think users opened suspicious message files before patching, treat their credentials as possibly exposed. Reset passwords for those accounts, starting with privileged ones, and look at outbound connections from workstations to unfamiliar external hosts. That is ordinary incident-response practice, not specific guidance from Microsoft or CISA.
For CMMC and federal contractors: KEV deadlines bind federal civilian agencies, but contractors are routinely measured against them in practice. Logging the patch date for the Outlook and Barracuda fixes, with the build numbers you verified, gives you clean evidence for your next assessment.
For small shops: If you only do one thing this week, make sure every machine running desktop Outlook has the November Office update installed.
Sources
- NVD record for CVE-2026-124194
- CISA Known Exploited Vulnerabilities catalog (JSON feed)
- The Record: Microsoft's Patch Tuesday surpasses 1,000 bugs for second month in a row
- CyberScoop: Microsoft fixes over 1,000 vulnerabilities in November Patch Tuesday
- The Register: November Patch Tuesday boasts over 1,000 bugs but only one zero-day so far