OFFSEC · Offensive Security

The November Outlook zero-day is a 6.5 that leaks credentials, and Windows Update will not fix it

CVE-2026-124194 lets a crafted file make Outlook hand an NTLMv2 hash to an attacker's server. It is the only exploited flaw in Microsoft's November release, it ships in the Office channel, and the outbound NTLM exposure it rides on is a configuration choice defenders can close.

A moderate score on the month’s only exploited bug

The one vulnerability Microsoft says attackers are already using this month is not among its 63 critical fixes. CVE-2026-124194 is an Outlook spoofing flaw scored 6.5 and rated Moderate [1]. It leaks Windows credentials. It is listed as exploited in the wild and is the only zero-day in the November 2026 release [2].

The mechanism is simple to state. A user opens a crafted message file. Outlook then connects to a network location the attacker controls, without the external-content warning it would normally show. That connection carries the user’s NTLMv2 hash, which the attacker can relay to sign in as the user or crack offline [1]. Microsoft’s own wording, as reproduced by IT-Connect, is that exploitation requires network connectivity and user interaction [3].

This desk will not describe how the crafted file is built. The defensive point is that the bug turns one opened file into an outbound authentication attempt. Everything below is about stopping that attempt from succeeding or being useful.

What the record says

The weakness is classed as CWE-356, a user interface that does not warn of unsafe actions [2]. The CVSS 3.1 vector reported from the CVE record is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, giving a base of 6.5; one reproduction of Microsoft’s data also lists a temporal score of 6.2 [4]. SecurityOnline reports that Microsoft rates exploit code maturity as High and gives a 30-day EPSS probability of 1.6 per cent [2].

Affected products are Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024 [1]. Microsoft states that the Preview Pane is not an attack vector [5]. The victim has to open the file.

Microsoft has not named the attackers, the targets or the scale of the campaign, and has not published indicators of compromise [5][6]. The acknowledgement, as reproduced by SecurityOnline, credits Benoit Sevens working with Anthropic’s Claude, and a researcher known as nono [2]. CSO Online describes the credit as going to an Anthropic researcher who used Claude [1]. The two accounts are compatible but not identical.

Several outlets report that CISA added the flaw to its Known Exploited Vulnerabilities catalogue on 10 November with a federal remediation date of 24 November [2][7][4]. This desk could not reach the catalogue itself. The Center for Internet Security’s MS-ISAC advisory states that Microsoft reports CVE-2026-124194 has been exploited, and rates the release High risk for large and medium government and business entities [8].

The fix is in Office, not Windows

This is the operational trap. The patch ships in Office updates, not the Windows cumulative update KB5132061 [5]. eSecurity Planet makes the same point: the Windows update alone does not cover it [6]. A fleet that reports fully patched Windows can still run a vulnerable Outlook.

Microsoft’s Office security release notes for 10 November list CVE-2026-124194 in the Outlook section, alongside 19 other Outlook CVEs [9]. The fixed builds are:

  • Current Channel: version 2610, build 20527.20196 [9]
  • Monthly Enterprise Channel: 2610 (20527.20194), 2609 (20430.20264), 2608 (20326.20320) [9]
  • Semi-Annual Enterprise Channel: 2610 (20527.20192), 2609 (20430.20262), 2608 (20326.20318) [9]
  • Office LTSC 2024: 2408, build 17932.21140; Office LTSC 2021: 2108, build 14334.21048 [9]

The LTSC builds match those in independent reporting [3][2].

Where the counts differ

Reported totals for the release disagree, and we publish them as found. CSO Online and SOCRadar give 1,094 vulnerabilities [1][5]. IT-Connect gives 1,093, excluding Edge [3]. Qualys headlines 1,235, while its own summary table totals 1,094 [7]. The critical count of 63 is consistent across sources [1][7][5]. The differences appear to come from what each counter includes; none changes the priority of the exploited bug.

What it means

The score understates the risk. Nick Carroll of Nightwing put it plainly: “Don’t let the low score fool you” [1]. A 6.5 rating reflects that the bug yields a hash rather than code execution. In a network where NTLM is accepted without signing or Extended Protection for Authentication, that hash can be relayed into services the user can reach [5]. Where passwords are weak, it can be cracked.

The bug is also a reminder that the exposure sits partly outside Outlook. An endpoint that can send NTLM to an arbitrary internet host is the precondition. That is a configuration decision, and it can be reversed independently of any one CVE.

Dustin Childs of the Zero Day Initiative said that a month with few active zero-days should not offer false comfort [6]. Tyler Reguly of Fortra noted that a vulnerability is not critical if the affected software is not deployed [1]. Outlook is deployed almost everywhere.

What to do

  • Deploy the November Office updates to every Outlook endpoint first, and verify the builds above through at least two signals, such as endpoint management reporting and a vulnerability scan [5].
  • Block outbound SMB on TCP 445 to the internet at the perimeter and host firewall [2][5].
  • Enforce SMB and LDAP signing, enable Extended Protection for Authentication, and place privileged accounts in Protected Users [5].
  • On Windows 11 24H2 and Windows Server 2025, enable the SMB client policy Block NTLM (LM, NTLM, NTLMv2) under Lanman Workstation, with an exception list for servers that cannot use Kerberos [10].
  • Set Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers to Audit all, review the NTLM operational log, then move to Deny all with defined exceptions [11].
  • Hunt for outbound NTLM using event 8001 in the NTLM operational log, and baseline NTLM volume on domain controllers with event 4776 [12].
  • Remind staff not to open unexpected message files; Microsoft lists no workaround other than the update [2][4].

Microsoft’s own hardening guidance recommends a phased approach to NTLM: baseline, audit, fix dependencies, then block in small projects starting with Tier 0 systems and privileged accounts [12]. Teams that have not started should begin with the audit step this week. It is non-disruptive and shows how much outbound NTLM the estate generates.

The rest of the release should not wait. CSO Online lists four flaws at 9.8, including an unauthenticated Windows LDAP remote code execution bug affecting domain controllers [1]. Qualys lists a set of unauthenticated network-reachable critical bugs in IIS, CredSSP, RPC Runtime and Schannel [7]. Those belong in the same change window as the Office update.

Offensive security close

CVE-2026-124194 is a small bug with a familiar payoff. Credential-leak flaws in mail clients recur because outbound NTLM is still permitted by default in many estates. Patching Outlook closes this instance. Restricting outbound NTLM closes the class. Teams should do both, and should confirm the Office channel actually delivered the build rather than trusting the Windows patch report.

Sources

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

  1. November 2026 Patch Tuesday: 63 critical Microsoft fixes, plus an Outlook zero day that allows theft of hashed credentials CSO Online · 2026-11-10
  2. Outlook zero-day CVE-2026-124194 SecurityOnline (Daily CyberSecurity) · 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. Outlook CVE-2026-124194 in CISA KEV: Fixed Office Builds Braindetox · 2026-11-11
  5. November 2026 Patch Tuesday: 1,094 Flaws, One Exploited SOCRadar · 2026-11-11
  6. Microsoft Fixes Outlook Zero-Day as November Patch Tuesday Targets 1,000+ Bugs eSecurity Planet · 2026-11-11
  7. Microsoft Patch Tuesday, November 2026 Security Update Review Qualys · 2026-11-10
  8. Critical Patches Issued for Microsoft Products, November 10, 2026 (MS-ISAC Advisory 2026-132) Center for Internet Security · 2026-11-10
  9. Release notes for Microsoft 365 Apps security updates Microsoft Learn · 2026-11-10
  10. Block NTLM connections on SMB Microsoft Learn · 2024-11-01
  11. Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers Microsoft Learn · 2022-06-15
  12. Active Directory Hardening Series - Part 8 – Disabling NTLM Microsoft Tech Community (Core Infrastructure and Security Blog) · 2026-01-14

Researched and written by the R3KONX Analysis Desk from the cited primary material. Microsoft's Security Update Guide entry for CVE-2026-124194 renders only with JavaScript and could not be read directly, and the CISA Known Exploited Vulnerabilities catalogue was unreachable; CVSS vector, acknowledgement and KEV dates are taken from the reproductions cited, and fixed builds from Microsoft's own Office release notes. 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.