Skip to main content
All incident reports
Incident report

Microsoft fixes exploited Outlook flaw that exposes Windows login hashes

Microsoft's November 2026 security updates fix an Outlook flaw that attackers are already using to capture Windows authentication hashes. Opening a crafted message file can make Outlook contact an attacker's server and hand over a hash that can be cracked or reused to sign in.

· First published · Last updated

The short version

  • The flaw. Microsoft's 10 November 2026 updates fix an Outlook spoofing flaw, CVE-2026-124194, rated moderate with a CVSS score of 6.5. Microsoft says it has been exploited in attacks.
  • How it works. A crafted message file, once opened, makes Outlook connect to an attacker-controlled location without the usual external-content warning and disclose the user's NTLMv2 hash, a Windows authentication credential. The hash can be cracked offline or used to impersonate the user.
  • Who is affected. Microsoft lists Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024. The Preview Pane does not trigger the flaw; a user has to open the file.
  • The patch count. Outlets put the November release between 1,093 and 1,259 flaws, partly because they count different sets of CVEs; Qualys counts 63 critical and 1,029 important-severity flaws. October's release was larger.
  • CISA listing. CISA has added CVE-2026-124194 to its Known Exploited Vulnerabilities catalogue, the list of flaws known to be used in real attacks.

Timeline

DateEvent
10 NovMicrosoft releases its November 2026 security updates, including a fix for the actively exploited Outlook flaw CVE-2026-124194.
11 NovBy 10 Nov: CISA had added CVE-2026-124194 to its Known Exploited Vulnerabilities catalogue.

The Outlook flaw and how an attack works

Microsoft released the fix on 10 November 2026 in its monthly Patch Tuesday bundle. The flaw is an Outlook spoofing bug tracked as CVE-2026-124194, rated moderate with a CVSS score of 6.5, and Microsoft says it has been exploited in attacks. Qualys reports it as the only flaw in the release that Microsoft says is being used in the wild; The Hacker News identifies it as the actively exploited Outlook bug.

An unauthenticated attacker sends a specially crafted message file and persuades the user to open it. Outlook then connects to an attacker-controlled network location without showing the usual external-content warning and discloses the user's NTLMv2 hash, a Windows authentication credential. The hash can be cracked offline or reused to impersonate the user and reach other systems. Microsoft says exploitation needs network connectivity and user interaction, and that the Preview Pane does not trigger the flaw.

Microsoft's advisory does not describe the observed attacks or name a threat actor, and The Hacker News notes that it does not say whether the flaw was discovered before or after exploitation began. Microsoft credits a researcher known as nono and Benoît Sevens, whose acknowledgement mentions Anthropic's Claude model.

Who is affected

Microsoft lists Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024 as affected products, and Krebs on Security reports the advisory as covering Microsoft 365 Apps for Enterprise and editions of Office. The user has to open the file; Microsoft says the Preview Pane cannot trigger the flaw.

A captured hash gives an attacker a way into the account behind it. Jack Bicer, director of vulnerability research at Action1, said a captured hash can let an attacker sign in as the victim, read their data and move to other systems, and that "The Moderate label undersells this one."

The wider November release

Sources differ on the size of the release. BleepingComputer and Qualys count 1,235 flaws, SecurityWeek 1,094 and Krebs on Security 1,093, and The Hacker News 1,259; the totals depend on what each outlet includes, and critical counts also differ. Qualys reports 63 critical and 1,029 important-severity flaws and 142 fixes for Chromium-based Edge. October's release was larger, at more than 1,400 flaws.

Microsoft has credited AI-assisted discovery for the growing volume, and outlets report it has now fixed more than 5,000 flaws in 2026. Other critical fixes this month cover remote code execution in Windows LDAP, Windows Search and Windows Schannel, and an elevation-of-privilege flaw in Azure OpenAI.

CISA has added CVE-2026-124194 to its Known Exploited Vulnerabilities catalogue. Chris Goettl, vice president of product management at Ivanti, noted that around 95,000 CVEs have been issued this year across vendors but only 217 have reached that list so far, and argued that teams should identify exposed assets and confirmed exploitation instead of treating every flaw as urgent.

What is not known yet

  • Who is carrying out the attacks; Microsoft has not attributed them to any threat actor.
  • How many organisations or users have been targeted, and whether captured hashes have been cracked and used to sign in.
  • Whether the flaw was found before attackers began using it or only afterwards.
  • What the malicious message files contain and how they are delivered beyond the requirement that a user opens one.

What to do

If you use Microsoft Outlook

  1. Install the November 2026 updates on every device running Microsoft 365 Apps for Enterprise, Office LTSC 2021 or Office LTSC 2024, checking Microsoft's advisory for the affected builds.
  2. Tell users that opening an unexpected message file can hand over their Windows credentials; the Preview Pane does not trigger the flaw, opening the file does.
  3. Review sign-in activity for accounts whose users may have opened suspicious message files, because a captured hash can be reused to sign in as that user.

If you manage patching

  1. Schedule the Outlook fix ahead of the rest of the November release, despite its moderate rating and its listing in CISA's exploited-vulnerabilities catalogue.
  2. Read Microsoft's advisory for the affected products and severity ratings instead of relying on news counts of the release, which differ between outlets.
  3. Back up important data before applying a large bundle of operating system updates.

For everyone else

  1. Establish what you actually expose to the internet before working through the rest of the release.
  2. Fix flaws known to be exploited in the wild first, then return the remainder to a normal patch cadence.

Update log

  • Added Qualys's review of the November release, which counts 1,235 flaws, including 63 critical and 1,029 important-severity vulnerabilities.
  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.