Outlook Zero-Day CVE-2026-124194: Opening One Message File Can Leak Your Windows Login Hash
Dr. Abeer Alshammari · Published 11/13/2026
Vulnerability Intelligence
- CVE
- CVE-2026-124194
- CVSS
- 6.5
- Affected product
- Microsoft Outlook for Windows (Microsoft 365 Apps for Enterprise, Office LTSC 2021 and 2024)
- Exploit status
- Actively exploited
- CISA KEV listed
- Yes
- Patch status
- Fixed in the November 2026 Office security updates (LTSC 2021 build 16.0.14334.21048, LTSC 2024 build 16.0.17932.21140); Microsoft 365 Apps fixed build depends on update channel
CyberAbeer's own prioritization guidance, based on severity, known exploitation, and exposure -- not an official vendor or CISA rating.
Sources last checked 11/13/2026
Bottom line: Microsoft patched an Outlook for Windows flaw (CVE-2026-124194) on 10 November 2026 and says it has detected exploitation. CISA added it to the Known Exploited Vulnerabilities catalog with a federal deadline of 24 November 2026. The CVSS score is a modest 6.5, but a crafted message file that makes Outlook reach out to an attacker-controlled location can expose Windows authentication material.
What happened
In its November 2026 Patch Tuesday release, Microsoft fixed a spoofing vulnerability in Outlook for Windows tracked as CVE-2026-124194. Microsoft reports that exploitation has been detected. The weakness is a missing warning: when a user opens a specially crafted message file, Outlook can connect to a network location chosen by the attacker without showing the usual external-content warning. Microsoft has not said who is behind the attacks or how many targets were affected, and no indicators of compromise have been published.
Why it matters
A medium score can hide a real operational risk. Reporting on the flaw indicates that the connection can leak the user's NTLMv2 authentication hash, which attackers may attempt to crack or relay to reach other systems. Because it is confirmed as exploited and listed in the CISA KEV catalog, it belongs in the urgent queue regardless of its CVSS number.
Who is affected
Outlook for Windows delivered through Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024, in both 32-bit and 64-bit editions. Fixed builds reported for the LTSC releases are 16.0.14334.21048 (2021) and 16.0.17932.21140 (2024). For Microsoft 365 Apps the fixed build depends on the update channel.
Technical impact
Exploitation needs user interaction: the target must open the crafted message file. Microsoft states the Preview Pane is not an attack vector. The outcome is disclosure of authentication information, not direct code execution, but credential material can be a stepping stone to lateral movement.
Governance impact
This is a good test of whether vulnerability management policy is driven by exploitation evidence or only by severity scores. Organisations that rank patches purely by CVSS may defer it. A risk-based policy should treat KEV listing as an automatic escalation trigger, and the patch status of Office clients should be reportable to the risk committee, not only to the endpoint team.
What security teams should do
Deploy the November 2026 Office security updates to every device running Outlook and confirm that Microsoft 365 Apps update channels have actually delivered the fix. Verify the build number in File, Office Account. Consider blocking outbound SMB and NTLM traffic to the internet, remind staff not to open unexpected message files, and review any device or account suspected of exposure as an incident.
What executives should know
An exploited flaw in the most widely used email client is a credential-theft exposure even when the headline score looks low. Ask for confirmation of Office patch coverage by the CISA date of 24 November 2026, and ask whether NTLM use is being reduced across the estate. For organisations in the MENA region, the same exposure applies to any Windows fleet running these Office releases.
Sources: Microsoft November 2026 Patch Tuesday coverage (Qualys, Suped, SecurityOnline) and the CISA KEV catalog entry as reported by those outlets. The primary Microsoft advisory page could not be opened directly during research, so details were cross-checked across these secondary reports.