The Outlook Zero-Day That Steals Your Hash: CVE-2026-124194, Exploited in the Wild

Microsoft's November Patch Tuesday fixed an actively exploited Outlook flaw: open one crafted message file and Outlook quietly reaches out to an attacker's server, handing over your NTLM authentication data for relay or offline cracking. Here's the mechanism, the fix, and the network control that neuters it.

3 min readIntermediate

Executive summary. CVE-2026-124194 is an actively exploited Microsoft Outlook vulnerability (a spoofing flaw, Microsoft rates it moderate / CVSS 6.5) that leaks a user's NTLMv2 authentication data. When a victim opens a crafted message file (reporting indicates opening the file, a higher bar than the old preview-pane bugs), Outlook is coaxed into reaching an attacker-controlled network path, and Windows automatically sends the user's NTLM hash over that connection. The attacker can then relay it to authenticate as the user, or crack it offline. It affects Microsoft 365 Apps, Office LTSC 2021 and Office LTSC 2024; the fix shipped in the November 2026 Office update. CISA added it to KEV with a 24 November federal deadline. The single most effective extra control: block outbound SMB (TCP 445) at the perimeter so the hash never leaves.

Outlook CVE-2026-124194 NTLM hash theft flow

What it is

Field Detail
CVE CVE-2026-124194
Product Microsoft Outlook (M365 Apps, Office LTSC 2021 / 2024)
Type Spoofing → NTLMv2 hash disclosure
Severity Moderate (CVSS 6.5) per Microsoft
Trigger Opening a crafted message file
Status Exploited in the wild; CISA KEV, deadline 24 Nov 2026
Fix November 2026 Office security update

How the hash walks out the door

NTLM authentication is automatic: when a Windows app connects to a file share or UNC path (\\host\share), Windows authenticates on the user's behalf, sending an NTLMv2 response derived from their password hash. The bug makes Outlook initiate such a connection to a path the attacker controls:

  1. The victim opens the crafted message file.
  2. Outlook reaches out to an attacker server over SMB/WebDAV.
  3. Windows sends the user's NTLMv2 authentication data automatically.
  4. The attacker relays it (to authenticate elsewhere as the user) or cracks it offline to recover the password.

Why "moderate" undersells it: the CVSS is modest because it needs user interaction and yields "only" a hash, but in a Windows domain an NTLM hash is a direct route to impersonation and lateral movement, especially where SMB signing isn't enforced (NTLM relay) or passwords are weak (offline cracking).

Remediation

Now

  1. Patch Outlook with the November 2026 Office update across M365 Apps and Office LTSC 2021/2024. Meet the 24 November KEV deadline.
  2. Block outbound SMB (TCP 445) and WebDAV to the internet at the firewall. This stops the hash from ever reaching an external attacker, and is good hygiene regardless.

Harden (defence in depth)

  1. Enforce SMB signing everywhere to break NTLM relay.
  2. Reduce NTLM: move toward Kerberos/modern auth; consider Group Policy to restrict outbound NTLM to remote servers.
  3. Strong passwords + MFA so a cracked or relayed hash is worth less.

Detection and hunting

Signal Why
Outbound SMB/WebDAV to external or unfamiliar hosts, especially shortly after a message file is opened The exfiltration channel
NTLM authentication to external systems Hashes leaving the environment
Outlook process making unexpected network connections The trigger in action
Spikes in NTLM relay indicators internally Follow-on use of stolen hashes

Hunt endpoint and firewall logs for Outlook-adjacent SMB egress; it's a strong, low-noise signal.

The pattern: "just a hash" is a foothold

NTLM-leak bugs recur in Office because the automatic-authentication behaviour is baked into Windows. Each one looks minor in isolation and becomes serious inside a domain. The durable fixes are structural: no outbound SMB, SMB signing on, and less NTLM overall, which blunt this entire class, not just this CVE.

Conclusion

CVE-2026-124194 turns one opened file into leaked credentials, and it's being exploited now. Patch to the November Office update to close it, but take the opportunity to block outbound SMB and enforce signing, which neutralises the whole family of hash-leak flaws.

Do this now: deploy the November Office update (KEV deadline 24 Nov), block outbound TCP 445/WebDAV at the perimeter, and alert on Outlook-driven external SMB connections.

Related: our network pentesting manual chapter on lateral movement explains NTLM relay and pass-the-hash.

Sources: CSO Online, SOC Prime, Netizen. Microsoft's Security Update Guide and the CISA KEV entry are authoritative.

HackersRoot Research · Research team

The HackersRoot research team investigates attack techniques across AI systems, cloud and identity, and enterprise networks, then publishes the detections and hardening guidance that stop them.

More from HackersRoot →

Related research