العربية
🚨 BreakingFBI Warns Artex AI Tool Automates Hacks at Machine Speed

Outlook Zero-Day CVE-2026-124194 Leaks NTLM Hashes: Patch Now

Security World Teamاقرأ بالعربية

November Patch Tuesday fixes an exploited Outlook zero-day: a crafted message file silently connects to an attacker's server and leaks the user's NTLMv2 hash.

Illustration for Vulnerabilities & CVEs
Illustration by Security World

⚡ Why it matters

NTLMv2 hashes can sometimes be cracked to recover the password, or relayed to other services to sign in as you. The flaw is being exploited now, and a Windows update alone does not fix it: Office itself must be updated.

In its November 2026 Patch Tuesday release, Microsoft fixed a Microsoft Outlook vulnerability tracked as CVE-2026-124194. It is classified as a spoofing flaw, and Microsoft confirmed it has been exploited in real-world attacks.

Vulnerability details

According to Microsoft's description, an unauthenticated attacker can send a specially crafted message file and persuade the user to open it. Outlook may then connect to a network location controlled by the attacker without showing the usual external-content warning, and during that connection Windows may send the user's NTLMv2 authentication hash.

  • Severity: CVSS 6.5 (medium).
  • Exploitation requires the victim to open the file; the Preview Pane is not an attack vector.
  • Affected products: Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024.
  • CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog on November 10, giving U.S. federal agencies until November 24 to patch.

How big is this month's release?

Counts depend on methodology: Microsoft's official release notes list 1,094 vulnerabilities, while BleepingComputer counted more than 1,200 after including other fixes. Either way, this is the only flaw confirmed as exploited this month.

What to do

  1. Install the November Office update on every machine that runs Outlook. Reported fixed builds: 16.0.17932.21140 for LTSC 2024 and 16.0.14334.21048 for LTSC 2021.
  2. Check the actual Outlook build on endpoints instead of relying on the deployment status in your management console.
  3. Block outbound SMB (TCP port 445) to the internet at the firewall.
  4. Review outbound NTLM restriction policies, and warn staff not to open unexpected message (.msg) files.

🔗 Sources

This article is original reporting by the Security World editorial team based on the sources listed above; direct quotes are kept short and marked with quotation marks. Corrections and feedback: info [at] securitywd.net.

Related stories