DEV Community

Anoymask
Anoymask

Posted on Edited on

Outlook CVE-2026-124194: Opening a Message File Triggers an External Connection Without Warning and Leaks an NTLM Authentication Response

1. Overview

  • Article Name: Microsoft November 2026 Patch Tuesday fixes 1,235 flaws, Outlook zero-day
  • Publisher: BleepingComputer
  • Published Date: 2026-11-10
  • Collection Date: 2026-11-11T07:47:50+09:00
  • Original Source: BleepingComputer
  • Related Source: Microsoft MSRC: CVE-2026-124194
  • Related Malware: None specified
  • Related Threat Group: None specified
  • Related CVE: CVE-2026-124194
  • Related Products and Technologies: Microsoft Outlook, Windows NTLM
  • Microsoft Severity: Moderate
  • CVSS v3.1 Base Score: 6.5 (Medium)
  • Response Priority (Author Assessment): Urgent
  • Priority Rationale: Confirmed exploitation and potential disclosure of NTLM authentication information warrant prompt patching.

2. Summary

When an unauthenticated attacker sends a crafted message file and a user opens it in Outlook, the application connects to an attacker-controlled network share without the usual external content warnings, potentially leaking the NTLMv2 authentication response (NetNTLMv2). Network reachability and user interaction are required.

3. Attack Flow

  1. An attacker sends a crafted message file to the victim.
  2. The victim opens the file in a vulnerable version of Outlook.
  3. Outlook or Windows connects to the attacker-controlled network location without displaying standard external content warnings.
  4. Automatic NTLM authentication transmits an NTLMv2 authentication response. An attacker may capture the challenge-response exchange for offline password cracking or relay the live authentication exchange to another service if its protections permit.

4. Attacker Position and Execution Location

  • An unauthenticated external attacker who delivers the message file and controls a network location reachable from the victim device.

5. Victim and Administrator Perspective

Victim Perspective

  • Opening the attachment may not trigger standard external content warnings, and there may be no prominent visual changes.

Administrator Perspective

  • Observable as external SMB or similar connections initiated by Outlook, or network access originating from the message file. Outbound NTLM audit logs are recorded based on endpoint settings.

6. Success and Failure Conditions

Success Conditions

  • A user opens the crafted file in a vulnerable version of Outlook.
  • The victim device successfully connects to the attacker-controlled network location and transmits NTLM.

Failure Conditions and Mitigations

  • Apply the fixed builds Microsoft publishes for each product and update channel (the November 2026 security update).
  • Block outbound SMB traffic to the internet and restrict outbound NTLM, denying it where possible. Configure auditing for detection.
  • Block suspicious message files and external network connections using mail gateways and EDR.

7. Impact of Successful Exploitation

  • The NTLMv2 authentication response (NetNTLMv2) may be disclosed. It is not the NT hash itself and cannot be used directly for Pass-the-Hash. Captured challenge-response data may support offline password cracking; relay attacks require relaying the authentication exchange to a service whose protections permit it.
  • Hash cracking, relay attacks, account impersonation using obtained credentials, and subsequent intrusion.

8. Observable Logs

  • Email: Delivery of the crafted message file, sender, attachment hash, and recipient.
  • Proxy/SWG/DNS: Resolution of unknown hosts and external connections immediately after opening the message file.
  • Endpoint/EDR: External network share connections originating from Outlook.exe.
  • Identity/IdP: Check for subsequent logins from unusual sources. Capture of an NTLM response by an attacker-controlled server alone need not generate a sign-in event in the organization's cloud IdP. Review endpoint NTLM audit logs where enabled; if relay or subsequent authentication is suspected, also review relevant destination-service and domain-controller logs.
  • SaaS/Cloud: Unusual logins to Microsoft 365 and other services using obtained credentials.
  • Network: External SMB/NTLM traffic and connections to attacker-controlled locations.

9. Attack Success Assessment

Information Theft or Session Compromise Confirmed

  • Public Information: Microsoft confirmed active exploitation of CVE-2026-124194, and BleepingComputer reported that the attack was used to steal NTLM account hashes.
  • Scope of Confirmation: Details regarding campaigns, victim counts, and subsequent intrusions are not publicly disclosed.

10. Investigation Playbook

  • Trigger: External SMB or NTLM connections immediately following the opening of an Outlook attachment.
  • Initial Verification: Check patch status, message file, sender, recipient, open time, and destination.
  • Endpoint: Preserve the Outlook process, recent files, network connections, and attachments.
  • Authentication & Cloud: Check for NTLM authentication and subsequent logins or sessions for the same user.
  • Subsequent Actions: Investigate hash relay, password cracking, account impersonation, and lateral movement.
  • Containment: Isolate the endpoint, apply patches, block external SMB, reset credentials, and revoke sessions.
  • Assessment Categories: Separate file delivery, user opening, forced authentication, hash acquisition, and subsequent account usage.

11. Defense and Detection Ideas

  • Single Event: Detect connections from Outlook.exe to internet SMB destinations.
  • Time-Series Correlation: Correlate attachment opening, outbound NTLM authentication, and subsequent anomalous logins by the same user.
  • Hunting: Search mail attachments and outbound port 445/TCP / NTLM events during the target period.
  • Log Gaps: Without linking message file opening and network authentication on the same device and user, determining success is difficult.
  • Priority Controls: Prioritize Outlook patches, external SMB blocking, NTLM reduction, and mail attachment controls.

12. Facts / Inference / Hypothesis

Facts

  • Microsoft patched CVE-2026-124194 as an actively exploited Outlook spoofing vulnerability.
  • Exploitation requires user interaction to open a crafted message file and a network connection.
  • Opening the file can connect to an attacker-controlled network location without standard external content warnings and disclose authentication information.
  • Windows may automatically transmit the NTLMv2 authentication response (NetNTLMv2) to a remote server. This is not the NT hash itself.
  • According to Microsoft, the Preview Pane is not an attack vector for this vulnerability; the user must actually open the crafted message file.
  • Affected products are Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024, and Microsoft publishes the fixed builds for each product and update channel (16.0.14334.21048 for Office LTSC 2021 and 16.0.17932.21140 for Office LTSC 2024).

Inference

  • Blocking external SMB and reducing NTLM usage reduces the attack surface until patches are applied, but does not replace product updates.

Hypothesis

No additional hypotheses. Unconfirmed items are listed in "Unknowns and Additional Investigation."

13. MITRE ATT&CK Mapping

ID Technique Confidence Basis
T1566.001 Phishing: Spearphishing Attachment medium Inferred if delivered as an email attachment. The exact delivery vector remains unconfirmed, but user interaction to open a crafted message file is required.
T1187 Forced Authentication high Forces transmission of NTLM authentication information via connection to an external network location.
T1078 Valid Accounts low Utilizing obtained credentials to gain access is possible, but subsequent success has not been publicly disclosed.

14. Unknowns and Additional Investigation

  • The public sources reviewed do not establish the actors behind the exploitation campaign, delivery vectors, victim organizations, or whether cracking or relay succeeded.

15. Impact on SOCs and Organizations

Because organizations widely retain Outlook and NTLM, credential disclosure involving user interaction still poses a risk of impacting authentication infrastructure. In addition to patching, verify that outbound SMB traffic to the internet is blocked and NTLM events are monitored.

16. Summary by Audience

  • For SOCs: Track external NTLM originating from Outlook and subsequent account usage.
  • For Administrators: Apply the November 2026 update and restrict external SMB and NTLM.
  • For Users: Do not open suspicious Outlook message files, and immediately contact administrators if opened.

Top comments (4)

Collapse
 
magopredator profile image
Fenix •

Severity: Critical

Collapse
 
anoymask profile image
Anoymask •

Thanks for highlighting this. Microsoft rates this vulnerability as Moderate, with a CVSS v3.1 score of 6.5 (Medium). I used “Severity” for my own response-priority assessment, which was misleading. I’ve corrected the article to separate the official rating from the urgency of patching due to confirmed exploitation.

Collapse
 
magopredator profile image
Fenix •

Has visto las noticias hoy? He visto las noticias y dicen sistema Microsoft caida mundial. Seguramente por esta vulnerabilidad, no? Muy bueno tu canal y tu labor Anoymash, gracias.

Collapse
 
magopredator profile image
Fenix •

Have you seen the news today? I saw that Microsoft systems are down worldwide. It’s likely due to this vulnerability, right? Your channel and the work you do are great, Anoymash—thanks!