Microsoft Confirms Active Exploitation of New Outlook Zero-Day (CVE-2026-124194) New

Outlook zero-day CVE-2026-124194 is being actively exploited. One click on a malicious message file can leak your NTLMv2 hash.

Microsoft has confirmed that attackers were exploiting a new Outlook zero-day before a patch was available. The flaw, tracked as CVE-2026-124194, was fixed in the 10 November 2026 Patch Tuesday release. It takes only one click on a malicious email file to leak a user’s login credentials, so update Office today.

Quick Facts

CVECVE-2026-124194
TypeOutlook spoofing / credential (NTLMv2 hash) leak
StatusActively exploited (zero-day), patched 10 November 2026
CVSS v3.16.5 (moderate)
CISA KEVAdded 10 November 2026, federal deadline 24 November 2026
AffectedMicrosoft 365 Apps for Enterprise, Office LTSC 2021 and 2024 (classic Outlook)
Fixed buildsLTSC 2024: 16.0.17932.21140 or later
LTSC 2021: 16.0.14334.21048 or later
Microsoft 365 Apps: varies by channel (see below)
User interactionOne click to open a crafted message file

What Is the Outlook Zero-Day?

The Microsoft Security Response Center says this Outlook spoofing flaw was exploited in the wild before the fix shipped. The patch is part of a huge November release, with more than 1,200 flaws fixed and 66 rated critical. Security researchers say this is the one to deal with first.

Most Outlook bugs that make headlines involve running malicious code. This one steals credentials instead. An attacker sends a specially crafted message file, and when the victim opens it, Outlook connects to a network location the attacker controls. Outlook does not show the usual external-content warning when this happens, so the user has no visual cue that anything is wrong.

How the Attack Works

  1. The attacker emails a crafted message file to the target.
  2. The user opens it, with no further interaction required.
  3. Outlook silently connects to an attacker-controlled server.
  4. That connection hands over the user’s NTLMv2 hash, a scrambled form of their login secret.
  5. The attacker uses the hash to authenticate as that user, read their data, and potentially move to other systems the account can reach.

Impact grows quickly if the victim is an administrator or works in finance. And because the warning users are trained to look for never appears, even careful staff can be caught out.

Why a “Moderate” Score Shouldn’t Fool You

With a CVSS score of 6.5, the flaw is not in the critical bracket, even though it is being actively exploited. Rapid7’s Adam Barnett points out that the score understates the value of this bug. It is useful both to commodity attackers harvesting initial access at scale and to more sophisticated, targeted campaigns. The lesson for organizations is not to triage on CVSS alone. Known exploitation in the wild should move a vulnerability to the top of the queue.

How to Fix It

The fix is part of Microsoft’s 10 November 2026 Office security updates. Windows Update will not install it. The patch comes through Office’s own updater, so installing the Windows November update alone leaves Outlook vulnerable.

For individuals and small teams

  1. Open Outlook (or Word) and go to File → Office Account → Update Options → Update Now.
  2. Restart Outlook when the update finishes.
  3. Go to File → Office Account → About Outlook and compare your build number with the table below.

Fixed build numbers

Edition / channelFixed build (or later)
Office LTSC 202416.0.17932.21140
Office LTSC 202116.0.14334.21048
Microsoft 365 Apps, Current ChannelVersion 2610 (Build 20527.20196)
Microsoft 365 Apps, Monthly Enterprise ChannelVersion 2610 (Build 20527.20194) or Version 2609 (Build 20430.20264)
Microsoft 365 Apps, Semi-Annual Enterprise ChannelVersion 2610 (Build 20527.20192) or Version 2609 (Build 20430.20262)

The fixed build differs by channel even when the version number is the same, so check the number for the channel you actually run. Microsoft publishes the full per-channel list at aka.ms/OfficeSecurityReleases, and the official advisory is on the Microsoft Security Response Center.

For IT teams and enterprises

  1. Push the Office update now through your usual channel (Intune, Configuration Manager or your Microsoft 365 Apps update channel). Don’t rely on Windows patches for this one.
  2. Confirm the installed build on every endpoint against the table above. Don’t assume the rollout succeeded.
  3. Start with high-value accounts, such as administrators, finance staff, and executives.
  4. Don’t wait for a full test cycle on everything. If you are staging the 1,000+ November fixes, pull this one forward.
  5. Note the CISA deadline. The flaw is in CISA’s Known Exploited Vulnerabilities catalog, with a federal remediation date of 24 November 2026.

Extra hardening (general best practice)

These steps come from standard defenses against NTLM credential theft, not from the vendor advisory. They reduce risk but do not replace the patch.

  • Block outbound SMB (TCP 445) from workstations to the internet at your firewall.
  • Restrict or disable NTLM where your environment allows it.
  • Require MFA on email and remote access so a stolen hash is harder to use.
  • If you suspect someone opened a suspicious message file, reset that user’s password and review their sign-in activity.
  • Remind staff not to open unexpected message attachments, even from familiar senders.

Also Patch: Critical PHP Vulnerabilities (CVE-2026-109618 and CVE-2026-109619)

Separately, the UK’s National Cyber Security Center (NCSC) issued an alert on 21 October 2026 about a critical security issue in PHP. Under certain conditions, an out-of-memory error could cause memory corruption, leading to unauthenticated remote code execution on a PHP-running web server. The NCSC says all versions of PHP are affected, and a fix is available.

  1. Identify every system running PHP, starting with internet-facing servers.
  2. Update to the latest fixed PHP release.
  3. If you can’t update yet, apply the PHP Foundation’s temporary mitigations, or take the system offline until it is protected.
  4. If you can’t do either right away, check for signs of compromise and backdoors before upgrading.
  5. Watch for vendor updates to any appliances or software that bundle PHP.

The Bottom Line

One opened file is enough to expose a user’s credentials, and attackers were exploiting the bug before a fix existed. Update Office today (Windows Update alone won’t do it), verify the build number, and prioritize your most privileged users. If you run web servers, patch PHP too.


Sources

Scroll to Top