Security Digest · Nov 10, 2026 · Vulnerability · Other

Outlook Zero-Day CVE-2026-124194 Leaks NTLM Hashes

Exploited Outlook flaw leaks NTLMv2 hashes when a user opens a crafted file. Fixed in the Nov 10 Office updates and added to CISA KEV. Patch this week.

Our verdict

Patch this week

Attackers are using this to steal NTLM hashes, but a user has to open a crafted file and the fix arrives through the normal Office update, so deploy it this week and check that outbound SMB is blocked.

Who must act: Organizations running Outlook for Windows from Microsoft 365 Apps or Office LTSC 2021 or 2024 on domain-joined machines, especially where NTLM is still accepted and outbound SMB to the internet is open.

Who can relax: Users whose Office has already taken the November 10 update. Microsoft's advisory does not list Outlook on the web, Outlook for Mac or the mobile apps.

Affected
Microsoft 365 Apps for Enterprise (32-bit and 64-bit) before the November 10, 2026 security release
Microsoft Office LTSC 2021 before build 16.0.14334.21048
Microsoft Office LTSC 2024 before build 16.0.17932.21140
Fixed in
Microsoft 365 Apps for Enterprise: November 10, 2026 security release for your update channel
Office LTSC 2021 build 16.0.14334.21048
Office LTSC 2024 build 16.0.17932.21140
CVSS
6.5 (v3.1, vendor)
EPSS
1.9% (percentile 81)
CISA KEV
Yes, listed as known exploited
Exploitation
Exploited in the wild
Severity
Medium

What to do

  1. Install the November 10, 2026 Office security update on every Windows machine with Outlook. It ships through Office update channels, not the Windows cumulative update.
  2. Confirm the build under File > Office Account in Outlook and compare it with the fixed builds for your channel.
  3. Block outbound SMB (TCP 445) from workstations to the internet at the perimeter and on host firewalls.
  4. Restrict outgoing NTLM where you can with the 'Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers' policy, starting in audit mode.
  5. Tell staff not to open unexpected message or Office files, including ones that arrive as attachments from known contacts.

How to check if you are affected or compromised

  • Report Office build numbers from your endpoint tool and flag machines below 16.0.14334.21048 (LTSC 2021), 16.0.17932.21140 (LTSC 2024) or the November 10 build for your Microsoft 365 Apps channel.
  • Search firewall and proxy logs for outbound connections from workstations to internet addresses on TCP 445.
  • If NTLM auditing is enabled, review the Microsoft-Windows-NTLM/Operational log for outgoing NTLM authentication to hosts outside your network.
  • Microsoft has published no indicators of compromise as of Nov 11, 2026.

What happened#

Microsoft's November 10, 2026 Patch Tuesday fixed one vulnerability that was already being exploited: CVE-2026-124194, a spoofing flaw in Outlook. Microsoft marks it "Exploitation Detected" and not publicly disclosed. CISA added it to the Known Exploited Vulnerabilities catalog the same day, with a November 24 deadline for federal agencies.

The weakness is a missing warning (CWE-356). In Microsoft's words, "an unauthenticated attacker could send a specially crafted message file and convince a user to open it in an affected version of Microsoft Outlook. Opening the file could cause Outlook to connect to an attacker-controlled network location without displaying the usual external-content warning." The result, Microsoft says, is that the flaw "discloses a user's NTLMv2 hash to the attacker who could use this to authenticate as the user."

Microsoft rates it Moderate with a CVSS 3.1 base score of 6.5. The CVE record carries the same score. Microsoft has not said who is exploiting it, against whom, or how many victims there are. Tenable counts 1,093 CVEs in the release and notes this is the only one exploited as a zero-day.

Who is affected#

Microsoft lists three products, each in 32-bit and 64-bit editions:

  • Microsoft 365 Apps for Enterprise, before the November 10 security release for your channel
  • Office LTSC 2021, before build 16.0.14334.21048
  • Office LTSC 2024, before build 16.0.17932.21140

The advisory does not list Outlook on the web, Outlook for Mac or the mobile apps. The practical target is a Windows user on a corporate network, because the stolen item is a Windows credential.

Do you really need to act?#

Yes, within your normal patch cycle for exploited bugs, and without panic. Here is the honest picture.

What limits it: the user has to open a crafted file. Microsoft states that "the Preview Pane is not an attack vector," so simply receiving or previewing the email is not enough. The attacker does not run code on the machine. They receive an NTLMv2 challenge response, which is useful only if they can crack it offline (weak passwords) or relay it to a service that accepts NTLM and that they can reach.

What makes it matter: it is being used in real attacks, Outlook is on nearly every corporate Windows desktop, and getting one person to open an attachment is not hard. A relayed or cracked hash for a privileged user can lead to much more than one mailbox.

Your exposure depends on two things you control besides the patch. If workstations cannot make outbound SMB connections to the internet, the most common route for the hash to leave is closed. If your important services reject NTLM or require signing and channel binding, a captured hash is much harder to use. Organizations with both controls in place are at low risk even before patching. Organizations with neither should move quickly.

What to do now#

  1. Deploy the November 10 Office update. Coverage of the release points out that this fix comes through Office updates, not the Windows cumulative update, so a fully patched Windows machine can still have a vulnerable Outlook.
  2. On a single machine, open Outlook and go to File > Office Account > Update Options > Update Now. To trigger it from a script on Click-to-Run installs, run "C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user.
  3. Verify the build under File > Office Account > About Outlook. LTSC 2021 should show 16.0.14334.21048 or later and LTSC 2024 should show 16.0.17932.21140 or later. For Microsoft 365 Apps, compare with the November 10 entry for your channel on Microsoft's Office security releases page.
  4. Block outbound TCP 445 from client networks to the internet. This is worth doing regardless of this bug.
  5. Audit and then restrict outgoing NTLM with the group policy "Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers."
  6. Remind users that opening an unexpected message or Office file is the step the attacker needs.

How to tell if you were hit#

Microsoft has published no indicators of compromise as of November 11, 2026, and has not described the files used in the attacks. Detection therefore rests on the side effect: a workstation authenticating to a host it has no reason to talk to.

  • Search perimeter firewall and proxy logs for workstation connections to external addresses on TCP 445.
  • If NTLM auditing is on, review the Microsoft-Windows-NTLM/Operational event log for outgoing NTLM to servers outside your domains.
  • In sign-in logs, look for NTLM authentications by a user from a machine or address that user does not normally use, which can indicate relay.

If you find a likely leak, reset that user's password and review what the account accessed afterward.

Timeline#

  • — Microsoft releases the fix in the November Office security updates and marks the flaw as exploited. The CVE record is published.
  • — CISA adds CVE-2026-124194 to the KEV catalog with a due date of November 24, 2026.
  • — No indicators of compromise or attribution published.

Vulnerability records

  • CVE-2026-124194 · KEV 2026-11-10 · Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing over a network.

Sources

Original sources first: vendor and project advisories, CVE and government records, the discoverers’ write-ups. Every claim above links to one of these. See how the Security Desk works.

Original and primary sources

  1. Microsoft MSRC — CVE-2026-124194: Microsoft Outlook Spoofing Vulnerability msrc.microsoft.com
  2. CVE.org — CVE-2026-124194 cve.org
  3. CISA — Known Exploited Vulnerabilities Catalog cisa.gov
  4. Tenable — Microsoft's November 2026 Patch Tuesday Addresses 1,093 CVEs (CVE-2026-124194) tenable.com
  5. SecurityOnline — Microsoft Outlook Zero-Day CVE-2026-124194 Exploited in the Wild Before November Patch securityonline.info