HLD Pulse · Zero-day · 12 November 2026Actively exploited

Microsoft Outlook zero-day. One opened message can hand an attacker your NTLM credentials.

Microsoft’s November Patch Tuesday, released 10 November, fixed 1,235 vulnerabilities by BleepingComputer’s count. One of them, CVE-2026-124194, was already being used in attacks. A crafted Outlook message file can make Outlook connect to a server the attacker controls without showing its usual external-content warning, sending the user’s NTLMv2 authentication hash along with the request.

What happened

Microsoft classes CVE-2026-124194 as an Outlook spoofing vulnerability. In its words, an attacker can send “a specially crafted message file and convince a user to open it”, after which Outlook could “connect to an attacker-controlled network location without displaying the usual external-content warning, potentially disclosing authentication information.”

Microsoft has confirmed exploitation but has not said who is behind it, how widely it has been used or which organisations were targeted. No indicators of compromise have been published, so detection has to rely on behaviour rather than known-bad addresses.

Why a Moderate rating still matters

The flaw scores 6.5 on CVSS 3.1 and needs the victim to open the file. The Preview Pane is not an attack vector. It does not run code on the machine. Those facts keep the rating at Moderate.

What it gives an attacker is a user’s NTLMv2 hash. That hash can be cracked offline to recover a weak password, or relayed to another service that still accepts NTLM to log in as the user. For an attacker already sending phishing mail, a reliable way to collect credentials from anyone who opens an attachment is a useful first step into a network, which is why it is already being exploited.

Affected versions

  • Microsoft 365 Apps for Enterprise

    Builds before the November 2026 security update. Check Microsoft’s Office security release notes for the fixed build on your update channel.

  • Office LTSC 2024

    Fixed in 16.0.17932.21140. Earlier builds are vulnerable.

  • Office LTSC 2021

    Fixed in 16.0.14334.21048. Earlier builds are vulnerable.

Both 32-bit and 64-bit editions are affected. Build numbers as reported by SOC Prime.

Patch now

  1. 1Push the November 2026 Office security update to every device running Outlook. The Windows cumulative update does not include this fix, so a fully patched Windows machine can still be exposed.
  2. 2Confirm Outlook build numbers across the fleet rather than relying on deployment status. Devices on deferred or semi-annual Microsoft 365 channels may lag behind.
  3. 3Treat this as a priority despite the Moderate rating. It is being exploited, and CISA has set a 24 November deadline for US federal agencies.

Reduce credential exposure

  1. 1Block outbound SMB (TCP 445) to the internet at the perimeter and on endpoint firewalls. Microsoft recommends this for any network that does not need SMB to leave it.
  2. 2Turn on auditing for the policy "Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers", review what breaks, then move to deny where you can.
  3. 3Remind staff not to open unexpected .msg or other message attachments, including ones that appear to come from colleagues or suppliers.

Detect and respond

  1. 1Alert on OUTLOOK.EXE opening an SMB or WebDAV connection to an external or never-before-seen destination, especially shortly after a message file is opened.
  2. 2Review the NTLM Operational log (Applications and Services Logs > Microsoft > Windows > NTLM) for authentication attempts to internet hosts.
  3. 3For any user whose hash may have left the network, look for later logons with that identity from unfamiliar hosts or locations. Captured NTLMv2 hashes can be cracked offline or relayed.
  4. 4If exposure is likely, preserve logs first, then reset the password and revoke active sessions.

The rest of November Patch Tuesday

BleepingComputer counts 1,235 vulnerabilities in the release, 66 of them rated Critical. 48 of those are remote code execution flaws, including bugs in Active Directory Domain Services and Windows graphics font handling. About 639 of the fixes are in Windows itself.

Other outlets report figures closer to 1,094. The difference comes down to what is counted: Edge fixes and the 108 flaws Microsoft patched earlier in the month are included in some totals and left out of others. Microsoft’s Security Update Guide is the authoritative list. Whatever the number, most of it arrives through Windows Update, and the Outlook zero-day does not.