CVE-2026-124194: Microsoft Office Outlook Missing User Interaction Spoofing and NetNTLMv2 Hash Theft
Microsoft Office Outlook contains a critical spoofing and security feature bypass zero-day (CVE-2026-124194) actively exploited in the wild and cataloged by CISA KEV on November 10, 2026. By embedding crafted composite OLE moniker streams into emails or attachments, an attacker suppresses standard external content security prompts. When the victim opens the message, Outlook silently invokes Windows SSPI/SPNEGO to negotiate an outbound SMB or WebDAV connection to an attacker-controlled listener. This immediately leaks the user's NetNTLMv2 authentication hash. Adversaries relay these hashes into unconstrained Active Directory Certificate Services (AD CS) or offline cracking clusters, gaining domain administrator foothold without executing unauthorized binaries on the workstation. Hermes assigns this vulnerability an HTS score of 95 (CRITICAL).
HERMES THREAT SCORE & ENTERPRISE RISK EVALUATION
Target:Microsoft Office Outlook MSO/OUTLLIB Resource Validation Pipeline & Windows SSPI While CVSS v3.1 scores CVE-2026-124194 at a modest 6.5 (Medium) due to user interaction requirements and absence of direct memory corruption, Hermes diverges to HTS 95 (CRITICAL). In enterprise Active Directory architectures, silent forced authentication represents an immediate perimeter breach. The victim's NetNTLMv2 hash can be relayed via ntlmrelayx to AD CS Web Enrollment (ESC8) or LDAP signing bypasses within milliseconds, generating machine or domain certificates that establish permanent, unrevocable domain persistence without dropping files onto disk.
1. Executive Summary & Operational Context
Section titled โ1. Executive Summary & Operational ContextโMicrosoft Outlook is the ubiquitous corporate email, calendar, and task management client powering enterprise communications across global organizations. Because Outlook operates inside the authenticated Windows domain context, external resource handling must be rigorously partitioned to prevent coercion of the local Windows Security Support Provider Interface (SSPI).
On November 10, 2026, Microsoft and CISA disclosed active zero-day exploitation of CVE-2026-124194, a high-impact security feature bypass in Microsoft Office Outlook. By crafting specific composite moniker references inside incoming messages, attackers suppress the standard security prompt warning the user that external content is being retrieved from an untrusted location.
+-----------------------------------------------------------------------------------------+| CVE-2026-124194 KILL CHAIN |+-----------------------------------------------------------------------------------------+| [External Attacker] || โ || โผ Sends email with crafted composite OLE moniker || [Target Workstation: OUTLOOK.EXE] || โ || โโโบ MSO!HrCheckSafeAction() evaluation bypassed via malformed moniker path || โโโบ Windows SSPI SPNEGO initiates outbound SMB connection (TCP 445 / WebDAV) || โ || โผ || [Attacker SMB/HTTP Listener (ntlmrelayx / Responder)] || โ || โโโบ Captures victim NetNTLMv2 challenge-response hash || โ || โผ Relayed in real-time || [Enterprise Active Directory / AD CS ESC8 Endpoint] || โ || โโโบ Issues User/Admin X.509 Certificate โโโบ Full Domain Administrator Takeover |+-----------------------------------------------------------------------------------------+When the recipient opens the crafted email or attachment, Outlook automatically initiates an outbound SMB (port 445) or WebDAV (port 80/443) network session against an adversary-controlled IP address. During the initial SMB/SPNEGO negotiation, the Windows client automatically transmits the userโs NetNTLMv2 challenge-response hash, delivering domain credentials into the hands of threat actors without requiring malicious code execution on the workstation.
2. Root Cause Analysis & Technical Mechanics (CWE-863 / CWE-359)
Section titled โ2. Root Cause Analysis & Technical Mechanics (CWE-863 / CWE-359)โThe vulnerability resides within the moniker resolution and external reference verification pipeline in MSO.DLL and OUTLLIB.DLL.
Under normal security enforcement, when Outlook encounters an OLE object or Rich Text Format (RTF) encapsulation pointing to an external Universal Naming Convention (UNC) path (\\attacker.domain\share\resource.bin), the policy check MSO!HrCheckSafeAction evaluates the target URI against the Internet Explorer / Windows Security Zone settings. If the destination does not belong to the Local Intranet or Trusted Sites zone, Outlook halts execution and displays a modal warning dialog requiring explicit user confirmation before initiating outbound network traffic.
// Decompiled pseudo-code representation of vulnerable moniker dispatchHRESULT HrProcessOleExternalResource(IMoniker *pMoniker, DWORD dwFlags) { LPOLESTR pszDisplayName = NULL; pMoniker->GetDisplayName(pBindCtx, NULL, &pszDisplayName);
// Flawed validation: specific nested composite moniker types (e.g., FileMoniker nested // inside ItemMoniker or CompositeMoniker) bypass canonical UNC prefix inspection if (IsNestedCompositeMoniker(pMoniker)) { // VULNERABILITY: Security warning prompt is skipped due to improper flag propagation dwFlags |= ACTION_SUPPRESS_SECURITY_UI; } else { if (!HrCheckSafeAction(pszDisplayName, ZONE_INTERNET)) { return E_ACCESSDENIED; } }
// Coerces Windows SSPI / SPNEGO provider to bind to external UNC path return pMoniker->BindToObject(pBindCtx, NULL, IID_IUnknown, (void**)&pResource);}In CVE-2026-124194, attackers structure the OLE payload using composite monikers where an inner FileMoniker or custom COM binding is encapsulated in an asynchronous stream. During moniker parsing:
- The outer parser classifies the container as an internal application structure, failing to propagate the untrusted remote origin flag down the parsing stack.
- When
BindToObjectis executed, the runtime resolves the inner UNC string directly through Windows Object Linking and Embedding (ole32.dll/combase.dll). - The underlying Windows operating system attempts to establish an SMB transport session to resolve the UNC file descriptor.
- Because the request originates from a standard Windows process running under user context,
SSPIinvokes the Negotiate security package, transmittingNTLMSSP_NEGOTIATEand responding to the serverโsNTLMSSP_CHALLENGEwith the userโs NetNTLMv2 hash.
3. Attack Surface & Threat Actor Exploitation Vectors
Section titled โ3. Attack Surface & Threat Actor Exploitation VectorsโAdversaries weaponize CVE-2026-124194 through multiple attack vectors targeting corporate personnel:
Vector A: Targeted Spear-Phishing with RTF/DOCX Attachments
Section titled โVector A: Targeted Spear-Phishing with RTF/DOCX AttachmentsโAttackers send emails containing crafted Microsoft Word (.docx) or Rich Text (.rtf) attachments embedding the vulnerable composite moniker. When opened inside Outlook or Word, the document immediately calls out to the external SMB share before the user finishes reading the text.
Vector B: Direct Calendar and Meeting Invite Coercion
Section titled โVector B: Direct Calendar and Meeting Invite CoercionโAdversaries transmit iCalendar (.ics) meeting requests containing appointment descriptions with linked OLE objects. Opening the calendar item or accepting the invitation triggers the background connection.
Vector C: Cross-Protocol NTLM Relaying to Active Directory Certificate Services (AD CS)
Section titled โVector C: Cross-Protocol NTLM Relaying to Active Directory Certificate Services (AD CS)โOnce the SMB connection hits the adversaryโs relay server (running impacket-ntlmrelayx), the incoming NetNTLMv2 authentication is relayed to an unauthenticated AD CS HTTP web enrollment endpoint (/certsrv/certfnsh.asp) vulnerable to ESC8. The attacker obtains an X.509 client authentication certificate for the targeted user, escalating privileges to domain administrator within seconds.
4. Forensic Timeline & Threat Actor Execution Flow
Section titled โ4. Forensic Timeline & Threat Actor Execution FlowโsequenceDiagram autonumber actor Attacker as Threat Actor (External) participant Outlook as Victim Outlook Client participant SSPI as Windows SSPI (Local OS) participant Relay as Rogue SMB Listener (ntlmrelayx) participant ADCS as Enterprise AD CS (ESC8)
Attacker->>Outlook: 1. Inbound Spear-phishing Email with Crafted Moniker Outlook->>Outlook: 2. Parse OLE Moniker (Security Warning Suppressed) Outlook->>SSPI: 3. Resolve UNC Path (\\attacker.evil\share\art.ico) SSPI->>Relay: 4. SMB SYN (TCP 445) & NTLMSSP_NEGOTIATE Relay->>SSPI: 5. NTLMSSP_CHALLENGE (Server Challenge Nonce) SSPI->>Relay: 6. NTLMSSP_AUTH (Victim NetNTLMv2 Hash) Relay->>ADCS: 7. Forward HTTP Auth to /certsrv (NTLM Relay) ADCS-->>Relay: 8. Issue User X.509 Certificate Relay-->>Attacker: 9. Exfiltrate Certificate & Elevate to Domain Admin5. Detection Engineering & Hunting Queries
Section titled โ5. Detection Engineering & Hunting Queriesโtitle: Microsoft Outlook Outbound SMB Connection to Untrusted Subnetid: 5a8e3124-b04d-498c-8f92-c1e194f12419status: productiondescription: Detects Microsoft Outlook (OUTLOOK.EXE) initiating outbound TCP connections on SMB port 445 to non-private external IP addresses, indicative of CVE-2026-124194 forced authentication exploitation.references: - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124194author: Hermes Cyber Intelligencedate: 2026-11-12logsource: category: network_connection product: windowsdetection: selection: Image|endswith: '\OUTLOOK.EXE' DestinationPort: 445 filter_private_ranges: DestinationIp|cidr: - '10.0.0.0/8' - '172.16.0.0/12' - '192.168.0.0/16' - '127.0.0.0/8' - '::1/128' - 'fe80::/10' condition: selection and not filter_private_rangesfields: - ComputerName - User - Image - DestinationIp - DestinationPortfalsepositives: - Legitimate cross-site Azure Files SMB mounting if configured without VPN (highly discouraged)level: criticaltags: - attack.credential_access - attack.t1187 - attack.t1557.001 - cve.cve_2026_124194// Detect Outlook initiating outbound SMB connections to public InternetDeviceNetworkEvents| where InitiatingProcessFileName =~ "outlook.exe"| where RemotePort == 445 or RemotePort == 80 or RemotePort == 443| where not(ipv4_is_private(RemoteIP))| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, RemoteIP, RemotePort, RemoteUrl| extend Timestamp = TimeGenerated, Hostname = DeviceName| sort by TimeGenerated descindex=windows sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=3 Image="*\\OUTLOOK.EXE" DestinationPort=445 NOT (DestinationIp="10.*" OR DestinationIp="172.16.*" OR DestinationIp="172.17.*" OR DestinationIp="172.18.*" OR DestinationIp="172.19.*" OR DestinationIp="172.20.*" OR DestinationIp="172.21.*" OR DestinationIp="172.22.*" OR DestinationIp="172.23.*" OR DestinationIp="172.24.*" OR DestinationIp="172.25.*" OR DestinationIp="172.26.*" OR DestinationIp="172.27.*" OR DestinationIp="172.28.*" OR DestinationIp="172.29.*" OR DestinationIp="172.30.*" OR DestinationIp="172.31.*" OR DestinationIp="192.168.*" OR DestinationIp="127.*")| table _time ComputerName User Image DestinationIp DestinationPort# Hunt for recent outbound SMB traffic logged by Windows Defender Firewall or SysmonGet-WinEvent -FilterHashtable @{ LogName = 'Microsoft-Windows-Sysmon/Operational' Id = 3 StartTime = (Get-Date).AddDays(-3)} | Where-Object { $xml = [xml]$_.ToXml() $img = $xml.Event.EventData.Data | Where-Object { $_.Name -eq 'Image' } | Select-Object -ExpandProperty '#text' $dport = $xml.Event.EventData.Data | Where-Object { $_.Name -eq 'DestinationPort' } | Select-Object -ExpandProperty '#text' $dip = $xml.Event.EventData.Data | Where-Object { $_.Name -eq 'DestinationIp' } | Select-Object -ExpandProperty '#text'
$img -like '*OUTLOOK.EXE' -and $dport -eq '445' -and $dip -notmatch '^(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[0-1])\.|127\.)'} | Select-Object TimeCreated, Message | Format-List6. Remediation & Hardening Directives
Section titled โ6. Remediation & Hardening Directivesโ-
Apply Microsoft November 2026 Security Updates: Deploy the monthly cumulative update or Office patches immediately (KB5002653, KB5002660, or M365 Apps build
16.0.18627.20248or higher). Verify deployment using SCCM/Intune compliance dashboards. -
Block Outbound SMB at the Perimeter (Port 445): Strictly filter outbound TCP port 445 (SMB) at all corporate perimeter firewalls and egress routers. Endpoints should never initiate raw SMB handshakes to public routable IP space.
-
Enforce NTLM Restrictions & EPA on Active Directory:
- Configure Group Policy
Network security: Restrict NTLM: Outgoing NTLM traffic to remote serversset to Deny all. - Enforce Extended Protection for Authentication (EPA) and require LDAP channel binding across all domain controllers to neuter NTLM relaying.
- Configure Group Policy
-
Harden AD CS Web Enrollment (Mitigate ESC8): Disable the HTTP Certification Authority Web Enrollment endpoint (
certsrv) if not strictly required, or enforce HTTPS with EPA enabled.