Skip to main content
November 2026 Patch Tuesday: Patch Outlook CVE-2026-124194 First, Then 47 Pre-Auth Bugs

November 2026 Patch Tuesday: Patch Outlook CVE-2026-124194 First, Then 47 Pre-Auth Bugs

KU
· Founder & Chief Editor
• 8 min read•4 views

Microsoft shipped well over 1,000 CVEs on November 10. Only one is exploited, a CVSS 6.5 Outlook flaw that leaks NTLMv2 hashes and is on CISA KEV with a November 24 deadline. Here is the order we would patch in, and the curl and jq checks that build it.

Key takeaways

  • Microsoft's November 10, 2026 release fixed over 1,000 CVEs, and only Outlook spoofing flaw CVE-2026-124194 is exploited.
  • It scores CVSS 6.5 but leaks a user's NTLMv2 hash and sits in CISA's KEV catalog with a November 24 deadline.
  • Patch Office first, then the zero-click Windows Search bug CVE-2026-116928 on Exchange servers.

Microsoft's November 10 release has more than 1,000 CVEs and one under active attack: Outlook flaw CVE-2026-124194, which can disclose the user's NTLMv2 hash. It scores only CVSS 6.5, yet CISA's KEV catalog gives federal agencies until November 24. Update Microsoft 365 Apps and Office LTSC first, then the pre-auth network bugs.

Verified against

CVE-2026-124194 and CVE-2026-116928 details, affected Office builds and severity counts, against Microsoft's November 2026 CVRF document and Security Update Guide, the CISA KEV catalog, FIRST EPSS and Microsoft Learn's SMB and NTLM pages. Checked November 17, 2026.

Why nobody agrees on the number

The Register and CSO Online both report 1,094, and CSO adds that 63 were rated critical. Rapid7's Adam Barnett, writing in iTWire, gives 1,092 "own-product" vulnerabilities. ZDI's Dustin Childs says "about 1,090" in his review. Qualys writes 1,235 in its text while its own summary table totals 1,094.

Our own count from Microsoft's CVRF document (November 16 revision): 1,646 entries, of which 1,098 name Microsoft as CNA and 291 come from Chrome's CNA, mostly listed for Edge. Of the Microsoft-assigned CVEs, 1,093 have a version 1.0 revision dated November 10, and 63 of those are Critical. Whether a count includes late additions and third-party entries likely explains the spread, so "about 1,090 Microsoft CVEs, 63 Critical" is the defensible figure. The document marks one CVE exploited, none publicly disclosed, and 42 "Exploitation More Likely".

A 6.5 that outranks every 9.8

CVE-2026-124194 is classed as spoofing (CWE-356). Microsoft's FAQ: an unauthenticated attacker convinces a user to open a crafted message file in Outlook, which could make Outlook connect to an attacker-controlled network location without the usual external-content warning. The flaw discloses the user's NTLMv2 hash, which the attacker could use to authenticate as the user. The Preview Pane is not an attack vector.

The base vector is AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. Required interaction and no integrity or availability impact keep it at 6.5; Microsoft rates it Moderate. ZDI's Dustin Childs: "don't let the score lull you."

The ranking rests on evidence, not score. Microsoft's threat field reads Exploited:Yes, and CISA added the CVE to its Known Exploited Vulnerabilities catalog on November 10 with a due date of November 24, 2026 for federal agencies. No other CVE in the release carries either marker. Microsoft's acknowledgments list "Benoit Sevens using Claude with Anthropic" and "nono".

Compare CVE-2026-116928, the Windows Search remote code execution bug scored 9.8 and rated Critical. Microsoft says an attacker could send an email with a crafted attachment to the Windows Search component used by Exchange Server, Exchange processes it for indexing automatically, and "the recipient does not need to open the email or attachment." ZDI calls it a zero-click bug on a high-value target, but Microsoft reports no exploitation and rates it "Exploitation Less Likely". Patch it this week, after the bug already in use.

The patch order, as of November 17, 2026

TierWhatEvidenceDeadline we'd set
1. ExploitedCVE-2026-124194 in Microsoft 365 Apps, Office LTSC 2021 (fixed build 16.0.14334.21048) and LTSC 2024 (16.0.17932.21140)Exploited:Yes, CISA KEVBefore November 24
2. Pre-auth, no click, on exposed serversCVE-2026-116928 on Exchange hosts (Windows Server 2016 to 2025), LDAP CVE-2026-119958, Windows DNS CVE-2026-88218 and DHCP Server CVE-2026-88243CVSS 9.8, AV:N/PR:N/UI:NWithin 7 days
3. Pre-auth, no click, everywhere elseThe rest of the 47 Microsoft CVEs with that vector (our CVRF count), 44 of which Microsoft marks "Customer Action Required: Yes"Vector only, no exploitationNormal monthly ring
4. Everything elseThe remaining CVEs; our count has 1,032 Microsoft-assigned Important CVEs, 521 of them elevation of privilegeSeverity onlyNormal monthly ring

Tier 2 follows ZDI's Childs, who singles out network-facing DNS, DHCP, LDAP and Exchange and counts 30 CVEs that fit his definition of wormable. The two 9.8 DNS and DHCP bugs are rated Important, so a severity filter alone would miss them. This is the same rule we recommend for application dependencies in our SCA, SAST and DAST program: rank by exploitation first, reachability second, score last.

Build the list yourself

The CVRF API, KEV feed and EPSS are public JSON, so triage fits in a few curl | jq calls. Output below is from a run on November 17, 2026.

Bash
# 1. KEV status and EPSS for the CVEs you care about
CVES="CVE-2026-124194,CVE-2026-116928,CVE-2026-119958"
curl -s https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json \
    | jq -r --arg c "$CVES" '($c | split(",")) as $l | .vulnerabilities[]
      | select(.cveID as $id | $l | index($id)) | [.cveID, "KEV", .dateAdded, "due " + .dueDate] | @tsv'
CVE-2026-124194	KEV	2026-11-10	due 2026-11-24
curl -s "https://api.first.org/data/v1/epss?cve=$CVES" | jq -r '.data[] | [.cve, .epss, .percentile, .date] | @tsv'
CVE-2026-124194	0.016200000	0.764770000	2026-11-16
CVE-2026-119958	0.012790000	0.704760000	2026-11-16
CVE-2026-116928	0.011610000	0.676640000	2026-11-16

# 2. Pull Microsoft's November CVRF (about 18 MB) and list what Microsoft marks as exploited
curl -s -H 'Accept: application/json' -o nov.json https://api.msrc.microsoft.com/cvrf/v3.0/cvrf/2026-Nov
jq -r '.Vulnerability[] | select(any(.Threats[]; (.Description.Value // "") | test("Exploited:Yes")))
    | .CVE + "  " + .Title.Value' nov.json
CVE-2026-124194  Microsoft Outlook Spoofing Vulnerability

# 3. Tier 2 and 3 candidates: Microsoft-assigned, network, low complexity, no privileges, no click
jq -r '.Vulnerability[]
    | select(any(.Notes[]; .Type == 8 and .Value == "Microsoft"))
    | select(any(.CVSSScoreSets[]?; .Vector | test("AV:N/AC:L/PR:N/UI:N")))
    | [([.CVSSScoreSets[].BaseScore] | max), .CVE, .Title.Value] | @tsv' nov.json | sort -u | sort -rn > preauth.tsv
wc -l < preauth.tsv
47

EPSS barely separates these three: all sit between 1.1% and 1.7%. EPSS is a probability estimate; KEV and Microsoft's exploited flag record observed exploitation, so we rank them above it. Feed preauth.tsv to whoever owns each product, and drop the three entries Microsoft marks "Customer Action Required: No", which are Azure Front Door, Entra and Azure OpenAI issues Microsoft fixed on its side.

Cutting off the NTLM leak while you patch

Patching Office is the fix; the advisory lists no mitigations or workarounds. While it rolls out, three general NTLM hardening controls from Microsoft's documentation limit where credentials can go.

Block outbound SMB. Microsoft's guide to securing SMB traffic says to block TCP port 445 outbound to the internet at the corporate firewall, noting you rarely need it outside public cloud scenarios such as Azure Files and Office 365. It also calls outbound Windows Firewall rules for guest and public networks important for mobile devices and home workers not behind the corporate firewall.

Put privileged humans in Protected Users. Members of the Protected Users group cannot authenticate with NTLM to the domain, and the domain functional level must be Windows Server 2012 R2 or later. Microsoft warns never to add service or computer accounts, and to test before adding Domain Admins or Enterprise Admins, because members can only use Kerberos with AES and can be locked out.

Audit, then restrict, outgoing NTLM. The Restrict NTLM: Outgoing NTLM traffic to remote servers policy takes Allow all, Audit all or Deny all, and Microsoft warns that changing it may affect compatibility. Its best practice: select Audit all, review the log under Applications and Services Log\Microsoft\Windows\NTLM to see which servers receive NTLM, and add those to the remote server exceptions list before denying.

Where this breaks

Blocking 445 at the edge does nothing for a laptop on hotel Wi-Fi unless the host firewall rule is also deployed. The preauth.tsv filter skips AC:H bugs such as Critical Schannel CVE-2026-119952, which Microsoft marks "Exploitation More Likely". The FAQ names a "network location", not a protocol, so do not assume SMB is the only path out; the NTLM audit shows what leaves. Protected Users and NTLM denial break NTLM-only apps, hence audit first. As of November 17, Microsoft has not said when attacks began or who is behind them, and CISA lists ransomware use as unknown. For the Windows Search bug, every remediation Microsoft lists is a Windows update, and Rapid7 notes the patches are for Windows rather than Exchange, so an Exchange host that is current on Exchange but behind on Windows is still exposed.

Questions people ask

Is CVE-2026-124194 exploited in the wild?

Yes. Microsoft marks it Exploited:Yes, and CISA added it to the Known Exploited Vulnerabilities catalog on November 10, 2026, with a federal remediation deadline of November 24. It is the only exploited CVE in the release, so it goes first despite the 6.5.

Does the Outlook Preview Pane trigger CVE-2026-124194?

No. Microsoft's FAQ states the Preview Pane is not an attack vector. The user has to open a crafted message file in an affected Outlook build, which could then connect out without the external-content warning and disclose the user's NTLMv2 hash. That required action is why the vector says UI:R.

The call we'd make

Push the Office update to every Outlook client this week and confirm builds before November 24, then patch Exchange hosts for CVE-2026-116928 and LDAP, DNS and DHCP servers within seven days. Turn on outgoing NTLM auditing today: Microsoft says the policy needs no restart, and the log tells you what a deny would break. The caveat: Microsoft keeps revising the release, so rerun the jq checks before each ring. For the general triage method, see how we handle vulnerabilities in production.

Sources

Explore topics:SecurityNewsDevOps
React
Share this post
Cite this article
Plain text

Kiril Urbonas (2026). November 2026 Patch Tuesday: Patch Outlook CVE-2026-124194 First, Then 47 Pre-Auth Bugs. DevOpsNess. https://www.devopsness.com/blog/microsoft-patch-tuesday-november-2026-outlook-zero-day-cve-2026-124194

Markdown

[November 2026 Patch Tuesday: Patch Outlook CVE-2026-124194 First, Then 47 Pre-Auth Bugs](https://www.devopsness.com/blog/microsoft-patch-tuesday-november-2026-outlook-zero-day-cve-2026-124194) (Kiril Urbonas, DevOpsNess, 2026-11-17)

KU

Kiril Urbonas

Founder & Chief Editor

600 articles
View all articles by Kiril Urbonas

You might have missed

Evergreen posts worth revisiting.