The exploited Outlook flaw CVE-2026-124194: who is affected, how it works, and how to check you are fixed

Microsoft's November 2026 updates fix an Outlook flaw that attackers were already using. Opening a booby-trapped message file could make Outlook quietly connect to an attacker's server and hand over the information needed to impersonate you. Which versions are affected, the build numbers that fix it, and the two-minute check to see if your Outlook is up to date.

Published Facts checked 5 min read
Three steps for CVE-2026-124194. Check: in classic Outlook select File, then Office Account, and read the version and build under Product Information. Compare: Current Channel needs Version 2610 Build 20527.20196 or later, Office LTSC 2024 needs build 17932.21140, Office LTSC 2021 needs build 14334.21048. Update: Update Options, then Update Now; at work, your IT team controls updates. Until then, do not open unexpected message files.
Microsoft lists no workaround: the fix is the update.

On 10 November 2026, Microsoft released a fix for CVE-2026-124194, a “Microsoft Outlook Spoofing Vulnerability” that its Security Update Guide marks as exploited: attackers were using it before the fix was out. Microsoft rates it Moderate, with a CVSS score of 6.5. The same day, the US Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities catalog, giving US federal agencies until 24 November 2026 to fix it.

In short:

  • Affected: classic Outlook in Microsoft 365 Apps for Enterprise, Office LTSC 2024 and Office LTSC 2021, according to Microsoft’s list.
  • How it works: someone sends you a crafted message file and persuades you to open it. Outlook then connects to the attacker’s server without its usual warning and can leak a hash of your Windows sign-in, which the attacker can use to authenticate as you.
  • Previewing is not enough to trigger it. Microsoft says: “No, the Preview Pane is not an attack vector.” You have to open the file.
  • The fix is the November update. Microsoft lists no workaround, so check your build and update.

What the flaw does

Microsoft’s description: “An unauthenticated attacker could send a specially crafted message file and convince a user to open it in an affected version of Microsoft Outlook. Opening the file could cause Outlook to connect to an attacker-controlled network location without displaying the usual external-content warning, potentially disclosing authentication information that could be used to impersonate the user.”

The “authentication information” is specific. Microsoft’s FAQ says: “This vulnerability discloses a user’s NTLMv2 hash to the attacker who could use this to authenticate as the user.” NTLM is one of the ways Windows proves who you are to other computers on a network. With the hash, an attacker does not need your password to pose as you.

Microsoft has not said who is exploiting the flaw or how widely. As SecurityWeek noted, “the company’s advisory provides no information about the observed attacks.”

Who is affected

Microsoft’s Security Update Guide lists six affected products, all of them now with an update available:

  • Microsoft 365 Apps for Enterprise (32-bit and 64-bit): the classic Outlook that comes with a work Microsoft 365 subscription
  • Office LTSC 2024 (32-bit and 64-bit)
  • Office LTSC 2021 (32-bit and 64-bit)

Microsoft does not list the new Outlook for Windows, Outlook on the web, Outlook for Mac, Office 2019 or Office 2016 as affected by this flaw. Not being listed means Microsoft did not name them; it is not a statement that they are safe from every attack, so keep them updated too.

Is your Outlook fixed? The two-minute check

  1. In classic Outlook, select File, then Office Account (if you do not see Office Account, select Help). Microsoft’s version guide says the version and build are listed under Product Information.
  2. Compare your build with the November 2026 builds from Microsoft’s security update list for Microsoft 365 Apps. Your build should be this one or newer:
Update channel or productNovember 2026 build
Current ChannelVersion 2610 (Build 20527.20196)
Monthly Enterprise ChannelVersion 2610 (Build 20527.20194), also 2609 (Build 20430.20264) and 2608 (Build 20326.20320)
Semi-Annual Enterprise ChannelVersion 2610 (Build 20527.20192), also 2609 (Build 20430.20262) and 2608 (Build 20326.20318)
Office 2024 or 2021, bought retailVersion 2610 (Build 20527.20196)
Office LTSC 2024, volume licensedVersion 2408 (Build 17932.21140)
Office LTSC 2021, volume licensedVersion 2108 (Build 14334.21048)
  1. If your build is older, update. Microsoft’s update guide says: “In the Product Information section, choose Update Options > Update Now.”

If there is no Update Options button: Microsoft explains that “if Update Options is missing and there’s only the About button, you either have a volume license install or your company is using Group Policy” to manage updates. At work, that means your IT team decides when the update arrives; ask them whether the November 2026 security update is installed.

Decision tree for CVE-2026-124194. Do you use classic Outlook from Microsoft 365 Apps, Office LTSC 2024 or Office LTSC 2021? If no, Microsoft does not list your Outlook as affected; keep it updated anyway. Is your build at or above the November 2026 build for your channel? If yes, you are fixed. Is there an Update Options button under File, Office Account? If yes, choose Update Options, then Update Now. Otherwise, your organisation manages updates: ask your IT team.

Until you are updated

Microsoft lists no workaround or mitigation for this flaw, so the update is the only fix it offers. Because the attack needs you to open a file, ordinary care helps while you wait:

  • Do not open unexpected message files (for example .msg attachments), especially ones that arrive with urgency or from someone you do not know.
  • Check the sender before you trust a message. Our article on how to tell if an email is spoofed shows how to read the authentication results in its headers.
  • If you need to see what a file contains, Mailtria’s MSG viewer opens it in your browser rather than in Outlook, without uploading it, and blocks remote content by default. It is not a security scanner, and it does not make an unknown file safe, so the update still matters.

Frequently asked

Can just previewing an email trigger it? No. Microsoft’s FAQ says: “No, the Preview Pane is not an attack vector.” The attacker has to “convince a user to open” the crafted file.

What does the attacker get? Your NTLMv2 hash, which Microsoft says the attacker “could use this to authenticate as the user.”

Is the new Outlook affected? Microsoft does not list the new Outlook for Windows, Outlook on the web or Outlook for Mac among the affected products for this flaw.

I have Microsoft 365 at home. Am I affected? Microsoft’s list names Microsoft 365 Apps for Enterprise, the business version, not the home plans. Updating does no harm either way: select File, then Office Account, then Update Options > Update Now.

What is the deadline? For US federal agencies, CISA set 24 November 2026. For everyone else, the advice is simply to update as soon as possible, since the flaw is already being used.

Is there a workaround if I cannot update yet? Microsoft lists none for this flaw. Avoid opening unexpected message files until the update is installed.

Sources

This article is general information, not legal, security or professional advice. Services change their rules and screens; check the official pages linked above before you act, and keep a backup before changing your mail.

MSG ViewerOpen an Outlook .msg email without Outlook. It runs in your browser; nothing is uploaded.
Open MSG Viewer