Skip to content

CVE-2026-124194: Microsoft Office Outlook Missing User Interaction Spoofing and NetNTLMv2 Hash Theft

Density:
C-Level Executive Briefing CVE-2026-124194 CRITICAL SCORE 95/100

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

HERMES THREAT SCORE & ENTERPRISE RISK EVALUATION

Target: Microsoft Office Outlook MSO/OUTLLIB Resource Validation Pipeline & Windows SSPI
Confidence: 98%
95 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 20 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 20 / 20
Impact 19 / 20
Exploit Maturity 20 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

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.


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 dispatch
HRESULT 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:

  1. The outer parser classifies the container as an internal application structure, failing to propagate the untrusted remote origin flag down the parsing stack.
  2. When BindToObject is executed, the runtime resolves the inner UNC string directly through Windows Object Linking and Embedding (ole32.dll / combase.dll).
  3. The underlying Windows operating system attempts to establish an SMB transport session to resolve the UNC file descriptor.
  4. Because the request originates from a standard Windows process running under user context, SSPI invokes the Negotiate security package, transmitting NTLMSSP_NEGOTIATE and responding to the serverโ€™s NTLMSSP_CHALLENGE with the userโ€™s NetNTLMv2 hash.

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.

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.


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 Admin

title: Microsoft Outlook Outbound SMB Connection to Untrusted Subnet
id: 5a8e3124-b04d-498c-8f92-c1e194f12419
status: production
description: 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-124194
author: Hermes Cyber Intelligence
date: 2026-11-12
logsource:
category: network_connection
product: windows
detection:
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_ranges
fields:
- ComputerName
- User
- Image
- DestinationIp
- DestinationPort
falsepositives:
- Legitimate cross-site Azure Files SMB mounting if configured without VPN (highly discouraged)
level: critical
tags:
- attack.credential_access
- attack.t1187
- attack.t1557.001
- cve.cve_2026_124194

  1. Apply Microsoft November 2026 Security Updates: Deploy the monthly cumulative update or Office patches immediately (KB5002653, KB5002660, or M365 Apps build 16.0.18627.20248 or higher). Verify deployment using SCCM/Intune compliance dashboards.

  2. 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.

  3. Enforce NTLM Restrictions & EPA on Active Directory:

    • Configure Group Policy Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers set to Deny all.
    • Enforce Extended Protection for Authentication (EPA) and require LDAP channel binding across all domain controllers to neuter NTLM relaying.
  4. 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.