OFFSEC · Offensive Security

November patch day: the exploited Outlook flaw scores 6.5, the SAP kernel bugs score 10

Microsoft's only exploited November bug is a Moderate-rated Outlook flaw that leaks NTLM hashes. SAP fixed four CVSS 10.0 flaws on the same day, two of them pre-authentication kernel bugs.

The exploited bug is the one scored 6.5

The only vulnerability confirmed as exploited in Microsoft’s November release is a Moderate-rated Outlook spoofing flaw, CVE-2026-124194, with a CVSS score of 6.5 [2][4]. It should be patched ahead of the release’s three CVSS 9.8 Windows flaws, none of which is reported as exploited [2][3]. On the same day, SAP fixed four CVSS 10.0 flaws in its kernel and NetWeaver stack. Two of them allow unauthenticated code execution on systems in their default or common configurations [10][11][12]. No in-the-wild exploitation of the SAP flaws had been reported at publication [10][11][15]. For any organisation running both platforms, 10 November produced two separate emergencies with different clocks.

What the data says: Outlook

Microsoft describes CVE-2026-124194 as a flaw in which a crafted file, once opened, makes Outlook connect to an attacker-controlled network location without the usual external-content warning [1][3]. That connection can disclose the user’s NTLMv2 hash. The hash can then be cracked offline or relayed to authenticate as the user [2][3]. The user must open the file. CrowdStrike notes that the Preview Pane is not an attack vector for this CVE [2]. Affected products are Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024. The fixed builds are 16.0.14334.21048 for LTSC 2021 and 16.0.17932.21140 for LTSC 2024 [3]. Microsoft has given no detail of the observed attacks [3]. The MS-ISAC advisory repeats Microsoft’s statement that the flaw has been exploited in the wild and rates the risk High for large and medium government and business entities [6].

The US Cybersecurity and Infrastructure Security Agency (CISA) added the CVE to its Known Exploited Vulnerabilities catalogue on 10 November, with a federal remediation deadline of 24 November [1][7]. One operational detail matters more than the score. Because this is an Office fix, it is delivered through the Office update channel, not by Windows cumulative updates. Fleets that track only Windows Update compliance can therefore show as patched while remaining exposed [7].

What the data says: the rest of the Microsoft release

The size of the release is not settled. CSO Online reports 1,094 fixes [5]. IT-Connect and PDQ report 1,093, with IT-Connect noting that its figure excludes Edge [3][4]. Qualys gives a headline of 1,235, but its own product-family table sums to 1,094 [1]. CrowdStrike counts 1,252 vulnerabilities, including 68 Critical [2]. Most counts put the Critical figure at 63 [1][3][4][5]. The differences mainly reflect choices about whether Edge (Chromium) and Extended Security Update entries are counted. The figures here are published as each source reports them.

Three CVSS 9.8 flaws matter most for enterprise networks. CVE-2026-119958 is an unauthenticated remote code execution flaw in Windows LDAP that exposes domain controllers [2][3]. CVE-2026-116928, in Windows Search, can be triggered by an attachment that Exchange indexes automatically, without user interaction [2][3]. CVE-2026-112967, in the Xbox Live Networking Service, mainly affects consumer configurations [2]. Microsoft rates exploitation of the LDAP flaw as less likely. It rates two Active Directory Domain Services flaws, CVE-2026-118146 and CVE-2026-118148, as more likely to be exploited [3]. Eight Office Preview Pane remote code execution flaws and eight Hyper-V privilege-escalation flaws round out the high-priority set [2].

Sources disagree on the Exchange Server flaw CVE-2026-118207. Action1, quoted by CSO Online, lists it among four 9.8 flaws and says anyone able to email the organisation can trigger it [5]. CrowdStrike and IT-Connect score it 8.8 and say exploitation requires low-privileged authentication [2][3]. Until Microsoft’s own scoring has been checked, defenders should treat it as the higher of the two. IT-Connect also notes that Exchange 2016 and 2019 left extended support in October 2026, so this fix ships only for Exchange SE [3].

What the data says: SAP

Onapsis counts 43 new and updated SAP Security Notes, 12 of them HotNews [12]. SecurityWeek reports 42 [14], Pathlock counts 38 notes plus four GitHub advisories [13], and BleepingComputer reports 35 vulnerabilities [15]. The counts differ by method. All four sources agree on the four CVSS 10.0 notes: 3778530 and 3778556 (ICM2SHELL), 3798345 (PROXYGATE) and 3849308, a missing-authentication flaw in the NetWeaver AS ABAP SAML2 service provider, CVE-2026-120017 [12][13][15].

ICM2SHELL (CVE-2026-76964 and CVE-2026-89126) is a memory-corruption flaw in the kernel code that handles WebSocket traffic, shared by the Internet Communication Manager and the Web Dispatcher [10][14]. WebSocket support is enabled by default even where no application uses it, so an unused feature still exposes the system [5][10]. Onapsis says it supplied SAP with a working proof of unauthenticated code execution as the system administration user and reproduced the crash on every kernel release it tested [14]. The Web Dispatcher usually sits at the network edge, which makes it the most exposed component [10].

PROXYGATE (CVE-2026-89103) is in the SAP Gateway. Whether it can be exploited depends on the gateway’s proxy access control list. A permissive list, or a missing list combined with the default allow-all proxy mode, leaves the system vulnerable [11]. Both flaws affect out-of-maintenance kernels that may never receive a fix and must be upgraded [10][11]. BleepingComputer notes that CISA has listed 14 SAP flaws as exploited since November 2021 [15].

What it means

CVSS ranks severity, not risk. An NTLM hash leak needs a click and scores Moderate. It is still the one bug in this release with confirmed attacker use, and it feeds directly into relay and credential attacks against the rest of the estate [2][3]. The SAP flaws score 10 but have no reported exploitation. They sit in components that are often internet-facing, and they come with a vendor-built proof of exploitation [10][14]. Historically, the gap between SAP patch and SAP exploitation has been short [15]. The volume of Microsoft fixes is a third pressure. Fortra’s Tyler Reguly expects high counts to continue while long-hidden bugs surfaced by automated discovery are fixed, and he advises teams to keep their prioritisation process rather than react to coverage [5].

What to do

  • Push the November Office update and confirm Office build numbers directly, not Windows Update status; target completion before the 24 November KEV date [3][7].
  • Reduce NTLM exposure regardless of patch state: block outbound SMB from workstation subnets to the internet, and audit, then restrict, outgoing NTLM through Group Policy [7][8].
  • Where supported, enable SMB client NTLM blocking so that a coerced connection to a hostile server receives no NTLM material [9].
  • Patch domain controllers and Exchange next, then hosts running Windows Search with Exchange indexing, and Hyper-V hosts in their own maintenance window [2][5].
  • For SAP, patch internet-facing Web Dispatcher and ICM instances first. Where that is not yet possible, SAP and Onapsis describe disabling WebSocket upgrade as a temporary workaround that can break integrations; check HTTP logs for WebSocket use before applying it [10][12].
  • Inventory every SAP Gateway, set the proxy access-control mode to restrictive after patching, and keep gateway ports off the internet [11].
  • Watch for unexpected ICM or Web Dispatcher restarts and process-ID changes outside maintenance windows [10].

Close

The November cycle shows a recurring offensive-security pattern. Attackers chose the low-scoring credential-exposure bug, while the maximum-severity flaws sit unexploited for now. Teams that triage only by CVSS would have patched the exploited flaw last. The useful signal is confirmed exploitation and exposure, then score.

Sources

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

  1. Microsoft Patch Tuesday, November 2026 Security Update Review Qualys Threat Research · 2026-11-10
  2. November 2026 Patch Tuesday attack surface analysis CrowdStrike · 2026-11-10
  3. Patch Tuesday — November 2026: Microsoft fixes 1,093 vulnerabilities, including an exploited Outlook zero-day IT-Connect · 2026-11-11
  4. Patch Tuesday November 2026 PDQ · 2026-11-10
  5. November 2026 Patch Tuesday: 63 critical Microsoft fixes plus an Outlook zero-day that allows theft of hashed credentials CSO Online · 2026-11-10
  6. Critical Patches Issued for Microsoft Products, November 10, 2026 (MS-ISAC Advisory 2026-132) Center for Internet Security / MS-ISAC · 2026-11-10
  7. CVE-2026-124194: Outlook NTLM hash theft Decryption Digest · 2026-11-11
  8. Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers Microsoft Learn · 2022-06-15
  9. SMB NTLM blocking now supported in Windows Insider Microsoft Tech Community · 2023-09-13
  10. ICM2SHELL (CVE-2026-76964, CVE-2026-89126): SAP NetWeaver and Web Dispatcher threat advisory Onapsis Research Labs · 2026-11-10
  11. PROXYGATE (CVE-2026-89103): SAP NetWeaver Gateway threat advisory Onapsis Research Labs · 2026-11-10
  12. SAP Security Patch Day: November 2026 Onapsis · 2026-11-10
  13. SAP Security Patch Day November 2026: critical vulnerabilities Pathlock · 2026-11-10
  14. SAP patches critical ICM2SHELL, ProxyGate vulnerabilities SecurityWeek · 2026-11-10
  15. SAP patches ICM2SHELL and PROXYGATE maximum severity flaws BleepingComputer · 2026-11-10

Researched and written by the R3KONX analysis desk from the cited primary material. Microsoft's Security Update Guide and SAP's support portal could not be retrieved directly, and cisa.gov was unreachable, so CVSS scores, fixed builds and KEV dates are taken from vendor research and security-press sources that state them. Release counts differ between sources and are reported as published. No exploitation of the SAP flaws had been reported at the time of writing. 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.