All CVEs

Outlook zero-day (CVE-2026-124194): opening a crafted message/Office file in classic Outlook leaks the user's NTLMv2 hash to an attacker, who can use it to sign in as the user. Exploited in the wild; CISA KEV added 10 Nov, due 24 Nov. Affects Microsoft 365 Apps and Office LTSC 2021/2024. Not zero-click: the Preview Pane doesn't trigger it. Fix is the 10 Nov Office update (e.g. Current Channel build 20527.20196), delivered through Office updates, not Windows Update. Check: File > Office Account > About Outlook. https://tldrcve.com/outlook-zero-day/

Microsoft Outlook · CVE-2026-124194

Outlook hash leak

Patch nowExploited, in CISA KEV (due 24 Nov). Update Office.

If a user opens a crafted Office file in classic Outlook, Outlook connects to an attacker's server without its usual warning and hands over the user's NTLMv2 hash. Attackers can use that hash to sign in as the user. Microsoft says it is being exploited; it is fixed in the 10 Nov 2026 Office update, not a Windows update.

How scary is it?

updated 20 Nov
  • Yes: Works without logging in1
  • Partly: Shown working, code not public1
  • Yes: Attacks seen in the wild1,4
  • Yes: On CISA's exploited list (fix by 24 Nov)3

Scare-o-meter

Drop everything

Attackers are already on it.
Patch now.

Are you affected? only if all are true

1Classic Outlook from a listed Office

Microsoft lists Microsoft 365 Apps for Enterprise, Office LTSC 2024 and Office LTSC 2021, 32- and 64-bit; retail Office 2021 and 2024 get the same Current Channel fix. Office Watch says new Outlook for Windows isn't affected and Outlook for Mac isn't on Microsoft's list.1,2,5

2Build older than the 10 Nov 2026 fix

In Outlook: File > Office Account > About Outlook. Fixed builds: Current Channel 2610 (20527.20196). Monthly Enterprise 2610 (20527.20194), 2609 (20430.20264) or 2608 (20326.20320). Semi-Annual Enterprise 2610 (20527.20192), 2609 (20430.20262) or 2608 (20326.20318). LTSC 2024 2408 (17932.21140). LTSC 2021 2108 (14334.21048).1,2,5

3A user opens the malicious file

The attacker has to get the user to open a crafted message or Office file. Microsoft says the Preview Pane is not an attack vector.1,5

What to do

1Update Office, not just Windows

The fix comes through Office's own updater, not a Windows cumulative update. In any Office app: File > Office Account > Update Options > Update Now, then restart Outlook. Admins: make sure your channel has reached the builds above (Intune, Configuration Manager or your Office update source).1,2,5

Latest safe versions checked 20 Nov

Microsoft 365 Apps → Current Channel2611 (20625.20108)Monthly Enterprise 261020527.20194Monthly Enterprise 260920430.20264Monthly Enterprise 260820326.20320Semi-Annual 261020527.20192Semi-Annual 260920430.20262Semi-Annual 260820326.20318LTSC 202417932.21140LTSC 202114334.21048Current Channel 2611's notes list no security fixes; it's newer than the fixed 2610 build.
2Retire Office 2016 and 2019

Microsoft doesn't list Office 2016 or 2019 for this CVE, though Office 2019 volume-licensed builds did get a 10 Nov update (1808, build 10417.20236). Office Watch assumes they're affected. Both are out of support: move those users to a supported Office.1,2,5

3Until patched: warn users

Microsoft lists no workaround. Tell users not to open unexpected message or Office attachments, and lean on your email gateway. Microsoft hasn't published indicators of compromise.1,4

This page shows you how to check. It can't tell you you're safe.

Sources (6) and changelog
  1. Microsoft MSRC: advisory, FAQ, affected products 10 Nov
  2. Microsoft Learn: Office security update builds 10 Nov
  3. CISA KEV catalog: added 10 Nov, due 24 Nov
  4. CSO Online: needs a user to open a file 10 Nov
  5. Office Watch: classic Outlook only, how to update
  6. Microsoft Learn: Microsoft 365 Apps update history