In November 2026, Microsoft confirmed active zero-day exploitation of CVE-2026-124194, a critical spoofing and credential-coercion vulnerability impacting Microsoft Outlook across both Microsoft 365 Apps and standalone enterprise Office installations.
By delivering crafted email notifications, meeting invitations, or OLE attachments referencing remote UNC paths (e.g., \\attacker-ip\share\sound.wav), threat actors force the Outlook client on the victim's endpoint to initiate an outbound SMB negotiation. During this automated handshake, the Windows client transmits the logged-in user's NetNTLMv2 hash directly to the adversary's listening server without prompting or user interaction.
In this security runbook, we break down the attack mechanics, provide PowerShell commands to audit outbound NTLM authentication, and detail how to enforce perimeter SMB blocking and Extended Protection for Authentication (EPA) in Exchange.
Anatomy of the CVE-2026-124194 Exploitation Flow
NTLM hash coercion represents one of the most persistent attack vectors against Windows environments. While Microsoft has announced plans to deprecate NTLM in Windows 11, legacy authentication protocols remain ubiquitous across enterprise environments.
The exploit chain operates as follows:
- Malicious Payload Delivery: The adversary sends an email containing an embedded UNC path within an appointment reminder or RTF document body.
- Automated Endpoint Trigger: When Outlook parses the message preview or fires a calendar notification, the Windows networking stack attempts to contact the remote UNC path via SMB (TCP port 445).
- Hash Capture: The attacker's server responds with an NTLM challenge. Outlook responds with the user's NetNTLMv2 authentication token.
- Offline Cracking or Relay: The adversary either cracks the hash offline using GPU clusters or immediately relays the hash against unprotected internal services (such as Active Directory Certificate Services or Exchange Web Services).
Defense Step 1: Blocking Outbound SMB (TCP 445) via Windows Defender Firewall
Even before an endpoint is patched, blocking outbound SMB at the host level prevents the Windows client from communicating with external attacker-controlled SMB listeners.
Run the following elevated PowerShell script to create an outbound firewall rule that blocks SMB traffic to all public Internet destinations while permitting internal LAN communications:
# Script: Block-OutboundPublicSMB.ps1
# Description: Mitigates CVE-2026-124194 by blocking outbound SMB to non-private subnets
$RuleName = "Block-Outbound-SMB-Public-CVE-2026-124194"
# Check if rule already exists
$Existing = Get-NetFirewallRule -DisplayName $RuleName -ErrorAction SilentlyContinue
if ($Existing) {
Write-Host "[i] Firewall rule '$RuleName' already exists. Re-enforcing..." -ForegroundColor Yellow
Set-NetFirewallRule -DisplayName $RuleName -Enabled True -Action Block
} else {
Write-Host "[+] Creating outbound SMB blocking rule: $RuleName..." -ForegroundColor Cyan
New-NetFirewallRule `
-DisplayName $RuleName `
-Name "Block_Outbound_SMB_Public" `
-Direction Outbound `
-Action Block `
-Protocol TCP `
-RemotePort 445, 139 `
-RemoteAddress "0.0.0.0-9.255.255.255", `
"11.0.0.0-172.15.255.255", `
"172.32.0.0-192.167.255.255", `
"192.169.0.0-255.255.255.255" `
-Profile Any `
-Description "Mitigates Outlook NTLM coercion zero-days by blocking outbound SMB to public IPs."
}
Write-Host "[✔] Outbound SMB blocked for public IPs. RFC1918 private subnets remain accessible." -ForegroundColor Green
Defense Step 2: Restricting Outbound NTLM via Group Policy
To permanently prevent Windows from sending NTLM credentials to remote servers, configure the following Group Policy Objects (GPO) or Intune Settings Catalog profiles:
1. Network Security: Restrict NTLM: Outgoing traffic to remote servers
- Path:
Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options - Setting:
Network security: Restrict NTLM: Outgoing traffic to remote servers - Recommended Value:
Deny allorAudit all(prior to full enforcement)
2. Configure via PowerShell for Immediate Local Enforcement:
# Enable NTLM Outgoing Restriction in Audit Mode to identify legacy internal dependencies
$RegPath = "HKLM:\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0"
Set-ItemProperty -Path $RegPath -Name "AuditAuditOutboundNTLM" -Value 1 -Type DWord
# Inspect Event Viewer: Applications and Services Logs > Microsoft > Windows > NTLM > Operational
# Event ID 8003 records all outbound NTLM authentication attempts.
Defense Step 3: Validating Extended Protection for Authentication (EPA) in Exchange SE / 2019
If an adversary captures an NTLM hash from a remote worker, their next objective is often relaying that hash against internal on-premises Exchange servers. Extended Protection for Authentication (EPA) binds the TLS channel certificate to the NTLM authentication token (Channel Binding Tokens - CBT), rendering relayed hashes mathematically invalid.
Ensure EPA is enabled across all Exchange virtual directories using the official Exchange Management Shell:
# Run in Exchange Management Shell on Exchange Server SE or 2019
$VDirs = Get-MapiVirtualDirectory, Get-WebServicesVirtualDirectory, Get-OabVirtualDirectory, Get-AutodiscoverVirtualDirectory
foreach ($vd in $VDirs) {
[PSCustomObject]@{
Server = $vd.Server
VirtualDirectory = $vd.Name
ExtendedProtection = $vd.ExtendedProtectionTokenChecking
}
}
If ExtendedProtectionTokenChecking reports None, enable it immediately across all servers:
# Enforce Extended Protection across Exchange Web Services (EWS)
Get-WebServicesVirtualDirectory | Set-WebServicesVirtualDirectory `
-ExtendedProtectionTokenChecking Require `
-ExtendedProtectionFlags "None"
# Enforce Extended Protection across MAPI over HTTP
Get-MapiVirtualDirectory | Set-MapiVirtualDirectory `
-ExtendedProtectionTokenChecking Require `
-ExtendedProtectionFlags "None"
# Restart IIS to apply bindings
Restart-Service W3SVC, WAS
Write-Host "[✔] Extended Protection for Authentication (EPA) enforced." -ForegroundColor Green
Defense Step 4: Endpoint Patch Verification
Verify that your endpoints have successfully installed the November 2026 security updates for Microsoft 365 Apps or Microsoft Office:
# Check current Outlook version via PowerShell
$OutlookApp = Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" -ErrorAction SilentlyContinue
if ($OutlookApp) {
Write-Host "Microsoft 365 Apps Build: $($OutlookApp.VersionToReport)" -ForegroundColor Cyan
Write-Host "Update Channel : $($OutlookApp.UpdateChannel)" -ForegroundColor Cyan
} else {
Write-Host "MSI Office installation detected. Check Windows Update history for KB5002xxx rollups." -ForegroundColor Yellow
}
Summary Checklist for Sysadmins
| Layer | Action | Impact |
|---|---|---|
| Edge Perimeter | Drop outbound TCP 445 / 139 at corporate firewalls | Blocks SMB traffic from internal subnets to public IPs |
| Endpoint Host | Deploy Windows Firewall outbound SMB block rule | Protects remote and roaming workers outside corporate VPN |
| Identity / GPO | Audit / Deny Outgoing NTLM traffic via GPO | Eliminates NTLM fallback across the operating system |
| Server Tier | Require Extended Protection for Authentication (EPA) | Neutralizes NTLM relay attacks against Exchange Server SE/2019 |
| Application Tier | Deploy November 2026 Office Security Rollup | Permanently patches the underlying parsing flaw in Outlook |