OFFSEC · Offensive Security

November Patch Tuesday: the exploited Outlook bug is moderate, the backlog is not

Microsoft's November 2026 release fixed roughly 1,100 CVEs, but only one was under attack: a 6.5-rated Outlook flaw that leaks NTLMv2 hashes. Defenders should patch it first, then work outward by reach to domain controllers and Exchange.

The one that is being used

Microsoft’s November 2026 security release contained one vulnerability confirmed as exploited in the wild, and it is rated Moderate. CVE-2026-124194 is a spoofing flaw in Microsoft Outlook with a CVSS 3.1 score of 6.5 [3][11]. Microsoft classes it under CWE-356, a user interface that does not warn of unsafe actions [11]. MS-ISAC flagged it in its advisory the same day: “Microsoft reports that CVE-2026-124194 has been exploited in the wild.” [5]

The mechanism matters more than the score. A victim opens a crafted message or Office file. Outlook then connects to an attacker-controlled network location without showing the usual external-content warning, and the connection discloses the user’s NTLMv2 hash [3][7]. That hash can be cracked offline or relayed to authenticate as the user elsewhere [3][7]. The victim has to open the file; Microsoft says the Preview Pane is not an attack vector [2][6].

CISA added the flaw to the Known Exploited Vulnerabilities catalogue on 10 November and set a remediation deadline of 24 November 2026 for US federal agencies [1][6][9]. Microsoft has not named the attackers, the targets or the scale of the activity, and has not published indicators of compromise [6][8][11].

Two operational details are easy to miss. First, the fix is delivered through Office security updates, not the Windows cumulative update, so a fully patched Windows estate can remain exposed [6][8]. Second, affected products are Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024; the fixed LTSC builds are 16.0.14334.21048 and 16.0.17932.21140 [7][11].

What the numbers say, and where they disagree

There is no single figure for the size of this release. CSO, SOCRadar and Qualys’s product table give 1,094 Microsoft CVEs [3][6][1]. PDQ and IT-Connect count 1,093, and SecurityOnline headlines 1,093 while its own breakdown by impact sums to 1,095 [4][7][9]. Qualys’s text cites 1,235 [1]. CrowdStrike counts 1,252 CVEs with 68 Critical, against the 63 Critical cited by most others [2][3][4]. The spread reflects different treatment of Edge, Extended Security Update products and third-party CVEs that Microsoft republishes, such as Chromium, OpenSSH and Linux kernel entries [2][9].

October’s comparison point also differs: IT-Connect and Ivanti’s Todd Schell put it at 1,407 CVEs, SOCRadar at 1,413 [7][12][6]. Either way, November is the second-largest Microsoft release on record [6][7].

The shape is consistent across counts. Elevation of privilege makes up roughly 43 to 49 per cent of fixes and remote code execution roughly a quarter [2][4][6]. Windows accounts for more than 700 CVEs and Office for between 174 and 201, depending on the source [1][4][7]. Microsoft flagged 42 further bugs as more likely to be exploited [9].

Several analysts attribute the volume to automated discovery. CSO reports that Microsoft has used its own AI model to find thousands of vulnerabilities since the summer, and that Microsoft credited a researcher using Anthropic’s Claude for the Outlook bug [3]. SOC Prime lists the credited researchers as “nono” and Benoît Sevens [11]. Accounts differ on the researcher’s affiliation, and we have not been able to confirm the acknowledgement text directly. Dustin Childs of the Zero Day Initiative said: “Logging back-to-back months above 1,000 CVEs proves automated bug-hunting has permanently reset patch volume.” [8]

What it means

Rating by score fails this month. The exploited flaw is rated 6.5 because it needs user interaction and does not by itself run code [11]. Its value to an intruder is identity: a captured NTLMv2 hash is a route into internal services, and Outlook is on almost every corporate desktop. Nightwing’s Nick Carroll put it plainly: “Don’t let the low score fool you.” [3]

The unexploited criticals carry the structural risk. CVE-2026-119958 is an unauthenticated 9.8 remote code execution flaw in Windows LDAP [1][10]. CrowdStrike notes that every domain controller exposes LDAP by design and that “the service cannot be disabled without breaking domain operations” [2]. Microsoft rates exploitation less likely and there is no published workaround [10]. CVE-2026-116928, a 9.8 Windows Search flaw, can be triggered by an attachment that Exchange Server indexes automatically, so the recipient never opens it [7][10]. Exchange itself carries CVE-2026-118207, an 8.8 authenticated code execution flaw [2][7]. Two Active Directory Domain Services flaws, CVE-2026-118146 and CVE-2026-118148, are rated more likely to be exploited [7]. CrowdStrike assesses that exploitation of the LDAP or AD DS flaws “can cascade to domain-wide compromise” [2].

There is also a coverage gap. Exchange 2016 and 2019 left Extended Security Updates in October and do not appear in this month’s fixes; IT-Connect warns they may still be vulnerable [7]. Ivanti’s pre-release forecast made the same point about end-of-life software more broadly [12].

What to do

  • Deploy the November Office updates to all Outlook endpoints first and confirm the fixed build on each device. Do not rely on the Windows cumulative update to close CVE-2026-124194 [6][7][11].
  • Block outbound SMB (TCP 445) to the internet, enforce SMB and LDAP signing, enable Extended Protection for Authentication, and place privileged accounts in Protected Users. These are general NTLM hardening measures, not a vendor workaround [6].
  • Audit outgoing NTLM using the ‘Restrict NTLM: Outgoing NTLM traffic to remote servers’ policy in audit mode before enforcing [11].
  • Hunt for Outlook activity followed by unexpected outbound SMB or NTLM authentication to external destinations, and for authentication by the same identity shortly afterwards. Treat these as leads, not proof [11].
  • Patch domain controllers next, as a set: LDAP, Kerberos, AD DS, Schannel and CredSSP [6][7]. Apply the Windows Server update and the Exchange SE update to Exchange servers in the same window [6][7].
  • Patch Hyper-V hosts for the eight Critical elevation-of-privilege fixes [1][6].
  • Plan migration for Exchange 2016/2019, Windows 11 23H2 Enterprise and Education, .NET 8 and 9, and PowerShell 7.4 as they leave support [6][7].
  • Verify deployment with at least two independent signals, such as endpoint management reporting and authenticated vulnerability scans [6][5].

Prioritise by exposure and deployment, not by headline count. Fortra’s Tyler Reguly framed it simply: “A vulnerability isn’t critical if you don’t have the impacted software deployed.” [3]

The offensive security view

For red and blue teams alike, the lesson is old. Coerced NTLM authentication remains one of the cheapest routes from a single opened file to an identity foothold. November’s exploited bug did not need code execution to matter. Estates that still allow outbound SMB and broad NTLM use will keep converting moderate client-side flaws into credential exposure, whatever the monthly CVE count says [3][6][11].

Sources

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

  1. Microsoft Patch Tuesday, November 2026 Security Update Review Qualys · 2026-11-10
  2. November 2026 Patch Tuesday: 1,252 CVEs Include One Zero-Day and 68 Critical Vulnerabilities CrowdStrike · 2026-11-10
  3. November 2026 Patch Tuesday: 63 Critical Microsoft fixes, plus an Outlook zero day that allows theft of hashed credentials CSO Online · 2026-11-10
  4. Patch Tuesday November 2026 PDQ · 2026-11-10
  5. Critical Patches Issued for Microsoft Products, November 10, 2026 (MS-ISAC Advisory 2026-132) Center for Internet Security / MS-ISAC · 2026-11-10
  6. November 2026 Patch Tuesday: 1,094 Flaws, One Exploited SOCRadar · 2026-11-11
  7. Patch Tuesday — November 2026: Microsoft Fixes 1,093 Vulnerabilities, Including an Exploited Outlook Zero-Day IT-Connect · 2026-11-11
  8. Microsoft Fixes Outlook Zero-Day as November Patch Tuesday Targets 1,000+ Bugs eSecurity Planet · 2026-11-11
  9. November 2026 Patch Tuesday SecurityOnline (Daily CyberSecurity) · 2026-11-10
  10. Microsoft Patch Tuesday November 2026: Windows Search and LDAP RCE, prepare now Rescana · 2026-11-10
  11. CVE-2026-124194: Microsoft Outlook Zero-Day Exploited to Steal NTLM Hashes SOC Prime · 2026-11-11
  12. November 2026 Patch Tuesday forecast: Old software continues to bite Help Net Security (Todd Schell, Ivanti) · 2026-11-06

Researched and written by the R3KONX Analysis Desk from the primary material cited below. Microsoft's Security Update Guide and the CISA KEV catalogue could not be retrieved directly; CVE details and the KEV listing are taken from vendor and CERT write-ups that reproduce Microsoft's and CISA's data. Monthly CVE totals differ between sources and are reported as published. 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.