Outlook NTLM Zero-Day: Patch Office, Block SMB

Outlook NTLM zero-day CVE-2026-124194: crafted message file leaks NTLMv2 hash, fixed in November 2026 Office update

An Outlook NTLM zero-day, CVE-2026-124194, is being exploited and sits in CISA’s list of exploited vulnerabilities. A user who opens a crafted message file makes Outlook connect to an attacker’s server without the usual external-content warning, and that hands over the user’s NTLMv2 hash. Microsoft fixed it on November 10 in the Office update. The CVSS score of 6.5 undersells it.

What Happened With the Outlook NTLM Zero-Day

Microsoft fixed the Outlook NTLM zero-day, CVE-2026-124194, on November 10 with its Patch Tuesday release. It rates the flaw Moderate (CVSS 6.5, weakness type “product UI does not warn user of unsafe actions”). The advisory marks it as exploited and says exploitation was detected. The flaw was not publicly disclosed before the fix.

Per Microsoft, an attacker sends a specially crafted message file and convinces a user to open it in an affected Outlook. Outlook then connects to an attacker-controlled network location without the usual external-content warning. That discloses the user’s NTLMv2 hash, which the attacker can use to authenticate as that user. The Preview Pane is not an attack vector, so the user has to open the file.

The fix comes through the Office update channel. Microsoft’s table lists updates for Microsoft 365 Apps for Enterprise, Office LTSC 2024 (build 16.0.17932.21140) and Office LTSC 2021 (build 16.0.14334.21048). CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10 and set November 24 as the deadline for US federal agencies. As of November 16, neither Microsoft nor CISA has named an attacker or described the campaigns, and the advisory lists no indicators.

Why It Matters

A hash works like a login. Anyone who holds the user’s NTLMv2 hash can try to authenticate as that user, with no malware on the endpoint and nothing for the user to notice. Assumption: in networks that still accept NTLM for file shares or internal apps, one opened file can be the first step toward those systems. Microsoft does not say how the stolen hashes are being used.

The score is a poor guide here. A CVSS of 6.5 reflects the required click and the missing impact on integrity and availability, but exploitation in the wild moves this flaw to the front of the queue. We made the same point on the SonicWall MFA bypass (CVSS 7.1) last week. For a Mittelstand company on Microsoft 365, desktop Outlook is on almost every machine, and NIS2 auditors will ask when the update reached it. Microsoft 365 Apps update on their own channel schedule, so Windows Update is not proof that Outlook is fixed.

What You Should Do Now

  1. Check the Office build on your clients and servers. Microsoft 365 Apps, Office LTSC 2021 and LTSC 2024 need the November update; compare against the build table at aka.ms/OfficeSecurityReleases. Do not assume the Windows cumulative update covered it.
  2. Block outbound SMB (TCP 445) to the internet at the perimeter, and from client networks where possible. This is our recommendation, not a Microsoft workaround. Microsoft does not say which protocol Outlook uses; SMB is the usual route for hash theft, and a web-based file-share connection could be another (Assumption).
  3. Turn on NTLM auditing, then restrict outgoing NTLM where nothing depends on it. Audit first, or you will break legacy applications.
  4. Check firewall and proxy logs since November 10, and further back if you can, for Outlook workstations connecting to unknown external hosts on port 445 or to unusual web-file-share hosts. Exploitation began before the patch and Microsoft gives no start date. If you find a hit, reset that user’s password and review their recent sign-ins.

DIESEC Perspective

Hash theft leaves little to see: a legitimate user opens a file, and nothing fails or alerts. Try this exercise: assume one user’s NTLMv2 hash left the building today and list the systems that would still accept it. That list is your NTLM exposure.

Not sure whether your Office builds and NTLM settings leave this gap open? Contact DIESEC for a rapid patch verification and NTLM exposure review.

Sources: Microsoft MSRC | CISA | SecurityWeek
Published: 2026-11-17 | Category: Vulnerabilities & Patches | ~4 min read