Skip to Content
← All articles

Microsoft Outlook: CVE-2026-124194 leaks the password hash

Opening one attachment in Outlook leaks the user's password hash. Microsoft shipped a fix on 10 November 2026; CISA wants it applied by 24 November.

Team Lumenax Nov 19, 2026 · 7 min read
Microsoft Outlook: CVE-2026-124194 leaks the password hash
November 19, 2026 by
Microsoft Outlook: CVE-2026-124194 leaks the password hash
Team Lumenax
A person reading email on a laptop
Photo: RDNE Stock project

Opening a single attachment in Microsoft Outlook can hand an attacker the user's password hash, with none of the usual warning about external content. Microsoft shipped a fix on 10 November 2026, and CISA added the flaw to its catalog of actively exploited vulnerabilities the same day, with a remediation deadline of 24 November 2026.

Key takeaways
  • The fix shipped on 10 November 2026; CISA listed the bug as actively exploited the same day.
  • Opening one attachment in Outlook is enough, no further user action is needed.
  • What leaks is the password hash (NTLMv2), not the password itself.
  • Affects Microsoft 365 Apps, Office LTSC 2021 and 2024, not Office 2019 or 2016.
  • CISA recommends fixing it by 24 November 2026.

CVE-2026-124194 affects Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024. A company with automatic Office updates turned on already has the fix. A company that delays or runs updates by hand is still exposed.

What happened

Microsoft released CVE-2026-124194 as part of its November security release ("2026-Nov"). It is a CWE-356 flaw: the user interface fails to warn about an unsafe action. Microsoft rates the severity "Moderate", CVSS score 6.5 (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N). NVD arrives at the same score, 6.5, MEDIUM.

The number alone doesn't look dramatic. Microsoft also flags the bug as actively exploited ("exploited: Yes"), and CISA added it to its Known Exploited Vulnerabilities catalog the same day. A low CVSS score and active exploitation aren't actually in tension: the attack needs no special privileges and no elaborate setup, just one opened attachment.

Microsoft splits the score into two sub-numbers that don't make it into the headline 6.5: exploitability 2.8 and impact 3.6. Impact is the higher of the two because the damage is high on one axis, confidentiality, not on all three, confidentiality, integrity and availability. The attack doesn't delete or disable anything; it only carries off one specific thing, credentials.

How the attack works

An attacker sends a specially crafted Office file and convinces the user to open it. Microsoft is explicit on this point: sending the file alone does nothing. Once opened, Outlook connects to a network location the attacker controls, without showing the usual external-content warning. That connection leaks the user's NTLMv2 hash, which the attacker can then use to authenticate as that user.

The Preview Pane is not an attack vector. Microsoft confirms this directly in its FAQ for the bug: viewing the file in preview carries no risk; it has to actually be opened. The gap between "it lands in the inbox" and "someone opens it" is exactly where staff training on attachments earns its place, not a technical fix.

This affects youYou run Microsoft 365 Apps for Enterprise, Office LTSC 2021 or Office LTSC 2024 without the November update.
Check firstYou're not sure when Office last updated, or you have laptops that haven't connected to the network in a while.
This doesn't affect youOffice is already on the build from 10 November 2026 or later.

Who is affected

  • Microsoft 365 Apps for Enterprise, versions before the fix delivered through the regular update (aka.ms/OfficeSecurityReleases).
  • Office LTSC 2021, versions earlier than 16.0.14334.21048.
  • Office LTSC 2024, versions earlier than 16.0.17932.21140.

Microsoft's vulnerability record does not list Office 2019 or Office 2016 among the affected products. That isn't confirmation they're safe: both are out of support, so no fix would ever be issued for them even if they shared the same flaw. A company still running either one gets no answer from Microsoft on this, only the fact that neither appears on the list of products being patched.

How to check

In Outlook, open File > Office Account > About Outlook and check the build number. Office LTSC 2021 needs build 16.0.14334.21048 or later, LTSC 2024 needs build 16.0.17932.21140 or later. For Microsoft 365 Apps for Enterprise, it's enough to have automatic updates turned on and to confirm the last update ran after 10 November 2026.

What to do

Neither Microsoft nor CISA describes any standalone workaround besides installing the fix. The required action in the CISA catalog points only to following vendor instructions, which here means updating. If updates run automatically, it's enough to confirm the last install date. If not, run it manually through Windows Update or Office Update, ideally by 24 November 2026, the date CISA set for US federal agencies and a reasonable guide for anyone else.

Until the update lands, the usual caution around unsolicited attachments matters a little more than usual: this hole is triggered by exactly that, a user opening an attachment.

For a company running its own IT, three things are worth checking: whether WSUS or Intune actually pushed the November update set to every machine, not just the one the admin tested on; whether anyone has automatic Office updates blocked because of an older add-in that doesn't get along with the new build; and whether laptops that haven't connected to the office network in a while will get the update at next login, not a month from now. None of this is specific to this one bug; it's the routine check that goes with every November release.

An IT engineer checking server status and update rollout
Checking that WSUS or Intune pushed the fix to every machine, not just the one the admin tested. Photo: Christina Morillo

Common questions

Does the attacker get my actual password?

Not in readable form. What leaks is the NTLMv2 hash of the password, not the password itself. Microsoft's FAQ for CVE-2026-124194 states the attacker can use that hash to authenticate as the user, so in practice it can be abused much like a password, just without the attacker ever needing to know it in readable form.

Is it enough for the attacker if I just preview the file in Outlook?

No. Microsoft's FAQ answers this directly: the Preview Pane is not an attack vector. The file has to actually be opened.

How do I know my Outlook version is safe?

For Office LTSC 2021 and 2024, by the build number (above); for Microsoft 365 Apps for Enterprise, by the date of the last update. Microsoft hasn't published a separate version number for 365 Apps because it updates through the regular channel.

Does this affect Office 2019 or 2016 too?

Microsoft's list of affected products doesn't include either one. Both are out of support, though, so no fix would come for them even if they turned out to share the same flaw.

Are ransomware groups already exploiting this?

The CISA catalog lists "Unknown" under "known ransomware campaign use" as of 13 November 2026. In other words, CISA neither confirms nor rules out a specific ransomware campaign.

What should I do if I can't update right away?

If you can't update right away Be more careful than usual with attachments from unfamiliar senders, and schedule the update as soon as you can, ideally by 24 November 2026.

Be more careful than usual with attachments from unfamiliar senders, and schedule the update as soon as you can. Neither Microsoft nor CISA describes any other mitigation for this specific bug.

Sources: Microsoft Security Response Center, CVE-2026-124194, published 10 November 2026 (msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124194); National Vulnerability Database, CVE-2026-124194 (nvd.nist.gov/vuln/detail/CVE-2026-124194); CISA Known Exploited Vulnerabilities Catalog, entry added 10 November 2026, catalog version 2026.11.13 (cisa.gov/known-exploited-vulnerabilities-catalog).

Team Lumenax

We write about security, AI and software for Czech companies with 10 to 100 people.

Cyber security
NÚKIB: How Russian Hackers Target VPNs and Firewalls
A 10 November 2026 NÚKIB analysis describes four common entry points and what to do about them.