OFFSEC · Offensive Security

November Patch Tuesday: the exploited Outlook flaw is the one severity filters drop

Of roughly 1,100 Microsoft CVEs, the only one under attack is a Moderate-rated Outlook bug that leaks NTLMv2 responses and ships outside the Windows update.

The exploited bug sits at the bottom of the severity table

Microsoft’s November Patch Tuesday landed on 10 November 2026. CyberScoop reports it is the second consecutive month whose count exceeds the totals of all previous years [3]. One flaw is confirmed as exploited in the wild: CVE-2026-124194, a spoofing vulnerability in classic Outlook [1][3]. Microsoft rates it Moderate with a CVSS 3.1 score of 6.5 [7]. Splashtop’s breakdown puts the release at 63 Critical, 1,029 Important and 1 Moderate. The Moderate one is the exploited Outlook flaw [5]. Any triage pipeline that starts from Critical will reach it last.

MS-ISAC rates the release High risk for large and medium government and business entities. The only exploitation it notes is CVE-2026-124194 [10]. No CVE in the release was publicly disclosed before patching [1][5].

What the flaw does

An unauthenticated attacker sends a crafted message file. If the recipient opens it, Outlook connects to an attacker-controlled network location without the usual external-content warning [4][6]. Windows can then send the user’s NTLMv2 authentication response to that server [7]. Microsoft classifies the weakness as CWE-356, a user interface that does not warn of an unsafe action [6]. The Preview Pane is not a vector [1].

The leaked response is not a password, but it is useful. It can be cracked offline or relayed live to services that lack SMB or LDAP signing or Extended Protection for Authentication [1]. ThreatDefence notes that relay to Active Directory Certificate Services can yield a certificate that survives a password reset [8]. The bug gives no code execution on its own [7]. Microsoft has not named attackers, targets, delivery method or scale, and no indicators have been published [6][8].

Affected products are Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024, in 32-bit and x64 builds [6][7]. Fixed builds are 16.0.14334.21048 for LTSC 2021 and 16.0.17932.21140 for LTSC 2024 [7]. ThreatDefence lists fixed Microsoft 365 Apps channel builds and notes that new Outlook, Outlook on the web, Mac and mobile clients are not listed as affected. It advises treating out-of-support Office 2016 and 2019 as exposed [8]. Microsoft’s acknowledgements credit a researcher using the handle nono and Benoît Sevens. SOC Prime and ThreatDefence report that the Sevens credit references use of Anthropic’s Claude [7][8]. CSO describes the credit differently, as going to an Anthropic researcher using Claude [2].

Why the patch can be missed

The Outlook fix ships through the Office update channel. It is not in the Windows cumulative update, KB5132061 [5]. Splashtop warns that fixes in Office, browsers and Adobe products arrive on separate schedules, so Windows-only reporting can mark devices as current when they are not [5]. ThreatDefence notes the fix ships in Office updates, not Windows Update [8].

Volume makes this worse. Rapid7 counts 1,092 Microsoft CVEs [1]. Cyber Security News counts 1,093, excluding fixes released earlier in the month [6]. CSO, CyberScoop and Splashtop give 1,094 [2][3][5]. Qualys headlines 1,235 but its own release table shows 1,094, without explaining the gap [4]. October’s figure also differs: BleepingComputer reported 1,411, CyberScoop and Splashtop 1,413 [13][3][5]. BleepingComputer links the volume to Microsoft’s use of AI platforms to find and fix bugs [13]. CSO links it to AI-assisted discovery since the summer but does not say all of it is AI-found [2].

ZDI’s Dustin Childs told CyberScoop that fewer zero-days exploited in the wild does not mean less exploitation overall. He suggested AI is better at reversing patches than at finding bugs in closed-source code [3]. If so, the gap between release and exploitation of the Critical bugs will narrow.

The Critical bugs that come next

CVE-2026-116928 in Windows Search is rated 9.8. Microsoft says an attacker can email a crafted attachment that Exchange indexes, with no user action [9]. ZDI calls it a zero-click bug on a high-value target [3]. CVE-2026-119958, a Windows LDAP flaw also rated 9.8, puts domain controllers at risk [2][9]. Neither is marked exploited or in the KEV catalogue [9]. Sources score the Exchange Server flaw CVE-2026-118207 differently: CSO reports 9.8, Splashtop 8.8 with exploitation more likely [2][5]. Splashtop also flags eight Critical Hyper-V privilege escalations and Critical bugs in Message Queuing, Schannel and CredSSP [5].

What to do

  • Push the November Office build to every machine running classic Outlook, and verify by Office build number, not Windows build [5][7].
  • Block outbound SMB to the internet at the perimeter and on roaming laptops [7][8].
  • Set the outgoing NTLM restriction policy to audit first, then deny with an exception list. Audit events land in the NTLM operational log on the client [12].
  • Enforce SMB and LDAP signing and Extended Protection for Authentication on Exchange and AD CS to blunt relay [1][8].
  • Hunt for Outlook making outbound SMB or WebDAV connections to external hosts shortly after a message file is opened, and for new NTLM logons that follow [7][8].
  • Then patch domain controllers, Exchange and internet-facing IIS, RPC and Message Queuing hosts [2][5].

Regional note

Many Asia-Pacific organisations triage from national CERT summaries. Singapore’s CSA alert AL-2026-160 publishes a table headed Critical Vulnerabilities with 68 entries. CVE-2026-124194 is not in it [11]. Teams in Malaysia and the region that work from Critical-only lists should add the exploited Outlook flaw and the KEV catalogue to their first pass. The lesson of this month is simple. Exploitation status outranks the severity label.

Sources

Every R3KONX article cites its primary material. 13 sources, in order of first citation. Links open the original publication.

  1. Patch Tuesday - November 2026 Rapid7 · 2026-11-10
  2. November 2026 Patch Tuesday: 63 Critical Microsoft fixes, plus an Outlook zero day that allows theft of hashed credentials CSO Online · 2026-11-10
  3. Microsoft fixes over 1,000 vulnerabilities in November Patch Tuesday CyberScoop · 2026-11-10
  4. Microsoft Patch Tuesday, November 2026 Security Update Review Qualys Threat Research · 2026-11-10
  5. November 2026 Patch Tuesday: Outlook zero-day leads 1,094 CVEs Splashtop · 2026-11-10
  6. Microsoft November 2026 Patch Tuesday Fixes 1,093 Vulnerabilities, Including Outlook Zero-Day Cyber Security News · 2026-11-10
  7. CVE-2026-124194: Outlook Zero-Day Exposes NTLM Hashes SOC Prime · 2026-11-11
  8. Outlook CVE-2026-124194 NTLM Zero-Day: Patching and Hunting ThreatDefence · 2026-11-12
  9. Microsoft Patch Tuesday November 2026: Windows Search and LDAP RCE, prepare now Rescana · 2026-11-10
  10. Critical Patches Issued for Microsoft Products, November 10, 2026 (MS-ISAC Advisory 2026-132) Center for Internet Security · 2026-11-10
  11. November 2026 Monthly Patch (AL-2026-160) Cyber Security Agency of Singapore · 2026-11-11
  12. Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers Microsoft Learn · 2022-06-15
  13. Microsoft October 2026 Patch Tuesday fixes 1,411 flaws, 3 zero-days BleepingComputer · 2026-10-13

Researched and written by the R3KONX Analysis Desk from the cited primary material. Vulnerability totals and some CVSS scores differ between sources and are reported as they differ; Microsoft has published no attacker, victim or indicator detail for the exploited flaw; hunting guidance is drawn from vendor research blogs, not Microsoft. Corrections: event@r3konx.asia.

R3KONX 2027

Work in this domain? So does the programme

4–6 May 2027, World Trade Centre Kuala Lumpur. Curated talks, hands-on training and The BattleGrid.