A missing warning changes the user's decision

Microsoft says CVE-2026-124194 affects Outlook when a user opens a specially crafted file. Outlook can then connect to an attacker-controlled network location without displaying the usual warning for external content. That connection may disclose the user's NTLMv2 hash, which an attacker could try to use to impersonate the user. Microsoft reports that exploitation has been detected, and CISA added the issue to its Known Exploited Vulnerabilities catalogue on 10 November.

Microsoft rates the flaw 6.5 under CVSS 3.1 and lists an official fix. The moderate numerical score does not erase the exploitation evidence. The exact update depends on the installed Office product and release channel, so defenders should use Microsoft's advisory to identify the applicable build.

Opening the file is required

Microsoft says the Preview Pane is not an attack vector for this CVE. The user must be convinced to open the crafted file, and the attack also needs network connectivity. A received message alone is not evidence of exposure.

Patch, then check for the authentication trail

  1. 1

    Identify affected Outlook installations. Check Microsoft 365 Apps and supported Office LTSC builds against Microsoft's product-specific update table. Prioritize users who handle untrusted message files or attachments, then verify the updated client is actually running.

  2. 2

    Review suspicious file activity. Correlate reported malicious files with Outlook and endpoint events. Establish which users opened them; do not count every recipient as compromised.

  3. 3

    Investigate outbound authentication. Look for unexpected NTLM authentication attempts from those clients to unfamiliar network destinations, then review subsequent sign-ins for affected accounts. Preserve timestamps, destinations and host context before response actions.

The disclosed hash is the lead, not the whole incident

A captured NTLMv2 hash is sensitive authentication material, but the advisory does not say every exposed account was taken over. Confirm the outbound connection and any later account activity separately. Where practical, limiting outbound NTLM to untrusted destinations can reduce this path's value to an attacker; the Microsoft security update remains the direct fix.