Outlook Zero-Day CVE-2026-124194 Leaks NTLM Hashes
By @sharedot · · 6 pages
- Cybersecurity
- Outlook Zero Day
- Ntlm
- Patch Tuesday
Microsoft's November Patch Tuesday fixed an actively exploited Outlook zero-day, CVE-2026-124194, that silently leaks NTLMv2 hashes.
A crafted message file, no warning, a stolen hash
Microsoft patched CVE-2026-124194 in its November 2026 Patch Tuesday release on November 10, describing a spoofing flaw in Outlook that carries a CVSS 3.1 score of 6.5.
An unauthenticated remote attacker can send a specially crafted Outlook message file and convince a victim to open it; Outlook then connects to an attacker-controlled network location without displaying the external-content warning users would normally see.
During that connection, Windows may expose NTLMv2 authentication information that could be abused to impersonate the victim. The company confirmed the flaw has already been exploited in attacks, though it has not disclosed the threat actors, campaign scale, or victims.
Microsoft credits researcher "nono" and Benoît Sevens with the report; SecurityWeek notes the acknowledgment references the use of Anthropic's Claude AI model during the research.
Why a 'Moderate' 6.5 zero-day still demands urgency
The CVSS score looks modest because exploitation requires user interaction and primarily affects confidentiality rather than enabling code execution.
The real risk lies in the affected technology: enterprise environments that still rely on NTLM for file shares, legacy applications, and internal authentication can let a leaked NTLMv2 hash be cracked offline or replayed to authenticate as the victim.
Notably, Microsoft states the Preview Pane is not an attack vector — the message must actually be opened. CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on November 10, setting a November 24, 2026 remediation deadline for applicable U.S. federal agencies.
SOC Prime's analysis argues defenders should prioritize confirmed exploitation status over CVSS alone when setting patch urgency, a stance Microsoft and CISA's actions effectively validate.
Hunting without IOCs: behavior over indicators
Microsoft has published no campaign-specific indicators — no malicious IPs, domains, attachment hashes, or sender addresses — so defenders must hunt behaviorally.
The strongest signal is OUTLOOK.EXE initiating SMB traffic toward an external or previously unseen destination shortly after a user opens a message file, especially outbound TCP port 445.
Microsoft recommends blocking outbound SMB to the internet as a defense-in-depth measure and points to the NTLM Operational log for auditing outgoing authentication.
Useful pivots include NTLM attempts toward internet destinations, successful internal authentication shortly after suspicious Outlook activity, and new logons inconsistent with a user's normal pattern.
Defenders are cautioned that outbound SMB and NTLM connections can be legitimate, so detections should correlate Outlook activity, destination reputation, and subsequent identity behavior rather than flag any single event.
Patch, verify, block SMB, then audit identities
The fix arrived with Microsoft's November 2026 Patch Tuesday: Office LTSC 2021 must reach build 16.0.14334.21048 or later, Office LTSC 2024 build 16.0.17932.21140 or later, and Microsoft 365 Apps for Enterprise should receive the current Office Security Release for its servicing channel, on both 32-bit and x64 systems.
Because exploitation is already underway, administrators should verify deployment rather than trust automated updates.
Microsoft also suggests the "Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers" policy, ideally run first in audit mode to map legacy dependencies before blocking.
If compromise is suspected, patching alone does not close the incident: teams should review authentication after the message was opened, and reset passwords and revoke sessions where exposure or abuse is evident.
Separately, BleepingComputer reports N-able rushed hotfixes for N-central zero-days that researchers began scanning for — a reminder that zero-day churn is running hot across the ecosystem this month.