Microsoft Patches Exploited Outlook Zero-Day CVE-2026-124194

Microsoft's Record Patch Tuesday Fixes 1,235 Flaws, Including Outlook Zero-Day

CRITICAL
November 12, 2026
November 18, 2026
5m read
Patch ManagementVulnerability

Related Entities(initial)

Products & Tech

Microsoft 365 Apps for EnterpriseMicrosoft Office LTSC 2021Microsoft Office LTSC 2024Microsoft Windows Search ComponentMicrosoft Outlook

CVE Identifiers

CVE-2026-124194
MEDIUM
CVSS:6.5
CVE-2026-116928
CRITICAL
CVSS:9.8

Full Report(when first published)

Executive Summary

Microsoft has released its November 2026 Patch Tuesday security updates, addressing an unprecedented 1,235 CVEs, the largest single monthly release on record. The update includes fixes for 66 critical vulnerabilities. The most urgent among them is CVE-2026-124194, a moderate-severity spoofing vulnerability in Microsoft Outlook that is being actively exploited in the wild. This zero-day flaw enables attackers to steal NTLMv2 credential hashes from victims with minimal user interaction. Due to the active exploitation, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added it to its Known Exploited Vulnerabilities (KEV) catalog, requiring immediate patching by federal agencies and strongly recommending it for all organizations.


Vulnerability Details

CVE-2026-124194: Microsoft Outlook Spoofing Vulnerability

  • CVSS Score: 6.5 (Moderate)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
  • Description: This vulnerability allows an unauthenticated, remote attacker to craft a special message file. When a user opens this file in an affected version of Outlook, the application connects to an attacker-controlled remote location (typically an SMB share) without displaying the standard security warning for external content. This connection attempt leaks the user's NTLMv2 hash. Attackers can capture this hash and use offline cracking tools to recover the user's password or use the hash in NTLM relay attacks (T1557.001 - Man-in-the-Middle: NTLM Relay) to authenticate to other services as the victim.
  • User Interaction: Requires the user to click and open a malicious file sent via email.

CVE-2026-116928: Microsoft Windows Search Component RCE

  • CVSS Score: 9.8 (Critical)
  • Description: A critical Remote Code Execution (RCE) vulnerability exists in the Windows Search Component. An attacker could exploit this by sending a specially crafted email that, when processed for indexing by an on-premise Microsoft Exchange Server, could trigger code execution on the server. This could potentially occur without any user interaction.

Affected Systems

  • CVE-2026-124194 affects the following products:
    • Microsoft 365 Apps for Enterprise
    • Microsoft Office LTSC 2021
    • Microsoft Office LTSC 2024
  • The November 2026 update addresses flaws in a wide range of products, including Windows, Office, Exchange Server, and others.

Exploitation Status

CVE-2026-124194 is confirmed to be actively exploited in the wild. On November 10, 2026, CISA added it to the KEV catalog, indicating observed, malicious cyber activity leveraging this flaw. Federal agencies are mandated to apply the update by November 24, 2026. The widespread use of Outlook in corporate environments makes this a high-priority vulnerability for all organizations, despite its moderate CVSS score.


Impact Assessment

The exploitation of CVE-2026-124194 can lead to widespread credential theft within an organization. Stolen NTLM hashes can grant attackers access to internal resources, facilitate lateral movement, and escalate privileges. Since the attack requires just one click and bypasses typical warnings, it is highly effective for initial access and internal reconnaissance. The CVE-2026-116928 flaw poses a severe risk to organizations running on-premise Exchange servers, as it could allow for a complete server takeover without user interaction.


Cyber Observables — Hunting Hints

The following patterns may help identify exploitation attempts related to CVE-2026-124194:

Type
network_traffic_pattern
Value
Outbound SMB traffic (TCP port 445) from workstations to external IP addresses
Description
This is a primary indicator of an NTLM hash leakage attempt. Corporate firewalls should block this traffic by default.
Type
log_source
Value
Windows Security Event Log ID 4625
Description
Monitor for failed logon events on external-facing servers where the source workstation name corresponds to an internal client, potentially indicating an NTLM relay attempt.
Type
url_pattern
Value
file://<external_ip>/...
Description
Email security gateways and EDR solutions should be configured to detect and block messages containing file:// URIs pointing to external resources.

Detection Methods

  • Network Monitoring: Implement strict egress filtering to block outbound SMB traffic (TCP/445 and UDP/445) from all client workstations to the internet. This is the most effective way to prevent NTLM hash leakage to external attackers. This aligns with D3FEND's Outbound Traffic Filtering.
  • Vulnerability Scanning: Use vulnerability management tools to identify all systems running affected versions of Microsoft Office and prioritize them for patching.
  • SIEM/EDR Alerting: Create detection rules to alert on outbound SMB connection attempts from endpoints. Correlate these alerts with email security logs to trace the source of the malicious file.

Remediation Steps

  1. Prioritize and Patch: Prioritize the deployment of the November 2026 security updates, with CVE-2026-124194 being the highest priority due to active exploitation. Apply updates via Windows Update, WSUS, or the Microsoft Update Catalog.
  2. Block Outbound SMB: If not already in place, configure perimeter firewalls to block all outbound SMB traffic from the corporate network to the internet. This is a security best practice that mitigates this and many other threats.
  3. User Awareness: Inform users about the threat of malicious email attachments and reinforce policies against opening unsolicited files, even if they appear to be simple documents.
  4. Harden NTLM: For further defense-in-depth, consider implementing policies to restrict or disable the use of NTLM in favor of Kerberos where possible.

Timeline of Events

1
November 10, 2026
Microsoft releases its November 2026 Patch Tuesday update.
2
November 10, 2026
CISA adds CVE-2026-124194 to its Known Exploited Vulnerabilities (KEV) catalog.
3
November 12, 2026
This article was published
4
November 24, 2026
Deadline for U.S. federal agencies to apply the patch for CVE-2026-124194.

Article Updates

November 18, 2026

New critical RCEs in LDAP, SharePoint, Exchange detailed; enhanced hunting hints and SMB signing remediation added.

Update Sources:

MITRE ATT&CK Mitigations

Applying the security updates provided by Microsoft is the primary and most effective remediation for these vulnerabilities.

Mapped D3FEND Techniques:

Blocking outbound SMB (TCP/445) traffic at the network perimeter is a critical compensating control that prevents NTLM hash leakage to external attackers.

Mapped D3FEND Techniques:

Educating users on the dangers of opening unsolicited attachments can reduce the likelihood of successful exploitation.

D3FEND Defensive Countermeasures

The primary and most effective countermeasure against the threats detailed in the November 2026 Patch Tuesday is the prompt application of security updates. For CVE-2026-124194, an actively exploited zero-day, patching is not just a recommendation but a critical and time-sensitive action. Organizations must use their patch management systems (e.g., WSUS, SCCM/MECM, or Intune) to deploy these updates immediately, prioritizing internet-facing systems and workstations with the affected Outlook versions. A risk-based approach should be taken, where systems belonging to high-value targets like executives or finance departments are patched first. Verification scans should be run post-deployment to ensure the update has been successfully applied across the enterprise and to identify any stragglers that require manual intervention. Given this is a KEV-listed vulnerability, compliance and security teams must track patching progress to completion.

As a powerful compensating control for CVE-2026-124194, organizations must implement strict outbound traffic filtering at their network perimeters. Specifically, blocking outbound SMB traffic (TCP port 445 and UDP port 445) from client subnets to the internet is essential. This single change breaks the attack chain by preventing the Outlook client from establishing a connection to the attacker's remote server, thus stopping the NTLM hash from ever leaving the network. This is a security best practice that mitigates a wide range of threats beyond this specific vulnerability. Network administrators should configure perimeter firewalls to deny this traffic by default. While implementing, it's important to audit for any legitimate business processes that might rely on outbound SMB (which is rare and generally insecure) and migrate them to a more secure file transfer method like SFTP or a managed file transfer solution.

Timeline of Events

1
November 10, 2026

Microsoft releases its November 2026 Patch Tuesday update.

2
November 10, 2026

CISA adds CVE-2026-124194 to its Known Exploited Vulnerabilities (KEV) catalog.

3
November 24, 2026

Deadline for U.S. federal agencies to apply the patch for CVE-2026-124194.

Sources & References(when first published)

Microsoft Fixes 1235 Flaws in Record Patch Tuesday
Infosecurity Magazine (infosecurity-magazine.com) •November 11, 2026
Microsoft November 2026 Patch Tuesday – Outlook Zero Day
Black Sheep Support (blacksheepsupport.co.uk) •November 11, 2026
Microsoft Patch Tuesday fixes Outlook flaw already under attack
Malwarebytes (malwarebytes.com) •November 10, 2026

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Editorial Standards & Analyst Review

CyberNetSec.io uses automation to assist source monitoring, deduplication, observable extraction, and structured intelligence generation. Published analysis follows human-defined editorial standards and adds defensive context including MITRE ATT&CK, D3FEND, STIX, and Sigma where applicable. Read our editorial policy.

Tags

Patch Tuesdayzero-dayOutlookNTLMCISA KEVCVE-2026-124194vulnerability

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

⚡ Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.