Steve Miller's Blog

Exploited Outlook Zero-Day Leaks NTLM Hashes: Why November’s Patch Tuesday Is the Moment to Start Retiring NTLM

Three anonymous IT security colleagues talk through a plan at a conference table with a closed laptop and blank notepads in a bright modern office.

When a Patch Tuesday ships more than a thousand fixes, the one that matters first is the one attackers already use. In November 2026, that is an Outlook zero-day, and it is an NTLM hash theft bug: open the wrong file and Outlook can hand your Windows authentication hash to a server the attacker controls. Patch it this week. Then use the scare to fix the real problem, which is a three-decade-old authentication protocol most of us keep around only because nobody has inventoried what still depends on it.

How the Outlook Zero-Day Enables NTLM Hash Theft

The bug is CVE-2026-124194, Microsoft Outlook Spoofing Vulnerability, released November 10. Microsoft’s Security Update Guide marks it Exploited: Yes and Publicly Disclosed: No, with an exploitability assessment of Exploitation Detected. Microsoft rates it Moderate with a CVSS 3.1 base score of 6.5. Affected products are Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024; the fixed builds listed are 16.0.14334.21048 for LTSC 2021 and 16.0.17932.21140 for LTSC 2024, with Microsoft 365 Apps covered through the normal Office security release channel.

The mechanics are short. According to Microsoft’s FAQ, an attacker sends a specially crafted message file and convinces the user to open it. Outlook then connects to an attacker-controlled network location without showing the usual external-content warning, and Microsoft says the flaw “discloses a user’s NTLMv2 hash to the attacker who could use this to authenticate as the user.” The Preview Pane is not an attack vector, so somebody has to actually open the file. Microsoft has not published details about the attacks it detected, so I am not going to guess who is behind them or how many organizations were hit.

CISA added the flaw to its Known Exploited Vulnerabilities catalog on November 10 and set a November 24 remediation due date for federal civilian agencies. If you are not a federal agency, treat that date as a sanity check, not a grace period.

Prioritizing One Fix Inside a Thousand-Fix Release

You may have seen this month described as a record. Microsoft’s own data does not support that. Counting CVEs in the November Security Update Guide data that were issued by Microsoft as the CNA and first published on November 10, I get 1,093. The same count for October 13 comes to 1,408. Both are enormous, but November is the smaller of the two, so it is not a record. Third-party tallies differ depending on whether they include Edge, Chromium, Linux, and other non-Microsoft CVEs that Microsoft republishes, so check what a headline number actually counts before you repeat it.

The practical point survives the correction. Severity sorting will not surface this bug on its own; a 6.5 Moderate sits below a long list of Critical ratings. The flags that should move it to the top are the exploitation status and the KEV listing. A workable triage order for a release this size:

  1. Exploited first. Anything Microsoft marks Exploitation Detected or CISA lists in KEV goes to the front, regardless of score. This month, that is the Outlook fix.
  2. Confirm the Office channel. Office fixes ride a different update path than the Windows cumulative update. Verify the build number on actual machines, not just the deployment ring status.
  3. Then the internet-facing and identity tier. Domain controllers, Exchange, and anything reachable from outside come next.

Why This Bug Class Keeps Coming Back

The patch closes one path. It does not change the underlying condition, which is that a Windows client will still offer an NTLM response to a server it should never have been talking to. Microsoft’s own description of NTLM, in its January 2026 post on disabling NTLM by default, lists the problems plainly: no server authentication, vulnerability to replay, relay, and pass-the-hash attacks, and weak cryptography. The same post notes NTLM has been part of Windows authentication for more than three decades and is already deprecated.

Imagine a finance user in a 40-person office who opens a message file that looks like a forwarded invoice. On an unpatched machine, the outbound connection happens, the hash leaves the building, and nobody sees a prompt. That is a hypothetical, but it is the shape of the risk: the user did one ordinary thing, and the protocol did the rest.

That is why the network layer matters as much as the patch. Microsoft’s guidance on securing SMB traffic says to block TCP port 445 outbound to the internet at the corporate firewall, and notes it is unlikely you need outbound SMB to the internet unless a cloud service such as Azure Files requires it. The same guidance recommends outbound firewall rules for laptops on untrusted networks, because those devices are not behind your perimeter firewall. I would put SMB signing and Extended Protection for Authentication on the same list for any service that still accepts NTLM, since both exist to blunt relay.

A Realistic NTLM Retirement Plan

Microsoft’s roadmap has three phases: enhanced NTLM auditing now on Windows Server 2025 and Windows 11 version 24H2 and later; IAKerb and a local Key Distribution Center, both described as pre-release, to remove common reasons for NTLM fallback, slated for the second half of 2026; and network NTLM disabled by default in the next major Windows Server and client releases. Disabled by default is not removed. Microsoft says NTLM will remain in the OS and can be re-enabled by policy, and its timelines are explicitly subject to change.

The steps Microsoft lists in that post are the right order of operations:

Notice what is not on that list: flipping a block switch on Monday morning. Audit before block. Every blocking control will break something you did not know about, often a printer, a scanner that writes to a share, or an old line-of-business app that only knows NTLM. The audit phase is how you find those before your users do. None of this is risk-free, and a staged rollout with a written rollback is cheaper than an all-hands outage call.

What I Would Do This Week

Push the Office update and verify builds. Confirm outbound 445 is blocked at the edge and test it from a laptop on guest Wi-Fi. Turn on NTLM auditing where your OS versions support it and let it collect for a few weeks. Then start the dependency list. The Outlook zero-day will be patched in a week or two. The NTLM inventory is the work that makes the next one of these a smaller story.

Exit mobile version