CVE-2026-124194: The Outlook Flaw Patched Two Days Before the Microsoft 365 Outage

At a glance

  • CVE-2026-124194, patched by Microsoft on 10 November 2026, let a disguised file make classic Outlook send a user’s NTLMv2 hash to an attacker’s server without the usual warning.
  • Microsoft confirmed it was already being exploited, and CISA added it to its Known Exploited Vulnerabilities list the same day.
  • Two days later, the Microsoft 365 outage gave attackers a ready-made lure, with fake “restore your messages” emails detected by 13 November.

On 10 November 2026, Microsoft released a fix for an Outlook flaw that attackers were already using. Two days later, Outlook, Teams and Copilot went down, with users in 74 countries and territories reporting problems within about an hour.

The two events are not connected, and Microsoft has said the outage was not the result of a cyberattack. But they landed in the same week, and that week shows clearly how flaws like this one are used in practice.

What Is CVE-2026-124194?

CVE-2026-124194 is a spoofing vulnerability in classic Outlook, fixed in Microsoft’s November 2026 security updates. Microsoft rates it Moderate, with a CVSS score of 6.5, and marked it as exploited at release.

Microsoft’s acknowledgement credits researchers who found it using Anthropic’s Claude AI model.

Wajahat Gondal, our Head of Risk Technology Development, describes it like this:

“The Outlook spoofing flaw (CVE-2026-124194) is a security vulnerability where attackers send a specially crafted email or file designed to look like a legitimate message or prompt.”

How Does the Outlook Flaw Work?

The attack depends on one ordinary action: a person opening something that looks routine. Wajahat explains what happens next:

“When an unsuspecting end user opens or clicks on the malicious item in Outlook, the program automatically attempts to authenticate with a remote server controlled by the hacker without showing a standard security warning. As a result, the user’s encrypted login credentials (specifically their NTLMv2 hash) are silently leaked in the background.”

Opening the file is the trigger, not reading the email. Rapid7 confirms that the Preview Pane is not an attack vector.

What Can an Attacker Do With an NTLMv2 Hash?

An NTLMv2 hash is a scrambled form of the user’s Windows credentials, used to prove who they are to network services. According to Rapid7, an attacker who captures one has two routes:

  • Relay it live to sign in as the user to another service, where protections such as SMB or LDAP signing are not in place.
  • Crack it offline to recover the password itself.

“Attackers can then crack these hashes or relay them to break into the user’s corporate network and email account meaning end users faced the risk of silent account takeover simply by interacting with a disguised file, even though merely viewing the email did not trigger the exploit.” – Wajahat Gondal

Rapid7 also warns that the 6.5 score “does not tell the full story”, because the flaw is useful to attackers harvesting access at scale.

Why Did the Microsoft 365 Outage Matter?

The outage began on 12 November 2026 and disrupted Outlook, Teams and Copilot. Al Jazeera reported that government systems in Singapore and Japan were among those affected.

By 13 November, Field Effect had detected phishing emails built around it. They carried these signs:

  • a subject line starting “Outage -“ followed by a six-character code
  • the real Exchange Online incident number, EX1550543
  • a claim that held messages would be deleted within 24 hours
  • a “RESTORE MESSAGES” button leading to a page that harvested logins

That lure and CVE-2026-124194 rely on the same instinct. A message that looks routine, arriving when people simply want things back to normal, is the one most likely to be opened.

The timing matters for IT teams too. A team spending Thursday and Friday restoring email may not yet have finished Tuesday’s updates.

What Should Organisations Do Now?

  1. Install the November 2026 Office updates. The fix ships through Office, not Windows Update, so check Outlook itself.
  2. Turn on SMB and LDAP signing, which Rapid7 identifies as the safeguard against relayed hashes.
  3. Audit and restrict NTLM, and look for outbound SMB or NTLM traffic from staff computers to external addresses.
  4. Check service status only through Microsoft’s own channels, never through a link in an email, even one quoting a real incident number.
  5. Test what one stolen credential could reach. A penetration test shows how far an attacker could move from a single compromised account.

Frequently Asked Questions

Does previewing an email trigger CVE-2026-124194?

No. Rapid7 confirms the Preview Pane is not an attack vector. The user has to open the crafted file.

Which versions of Outlook are affected?

Microsoft released patches for all supported versions of classic Outlook. Check your build against Microsoft’s Security Update Guide.

Does Windows Update fix it?

No. The fix is delivered through Office updates, so Outlook needs updating separately.

Was the Microsoft 365 outage caused by this flaw?

No. Microsoft said the outage was not the result of a cyberattack, and there is no published evidence linking the two.

A Flaw That Needed a Person

CVE-2026-124194 did not break through a firewall. It needed someone to open a file that looked legitimate, and the week of the outage showed how easily that moment can be arranged.

If you would like to know what an attacker could reach from a single opened file, read our guide to vulnerability assessment and penetration testing, or get in touch for a confidential conversation.