Skip to content
Outlook spoofing flaw exploited: update Office by Nov. 24

Outlook spoofing flaw exploited: update Office by Nov. 24

On November 10, 2026, CISA added CVE-2026-124194, a Microsoft Office Outlook spoofing flaw, to its Known Exploited Vulnerabilities (KEV) catalog. That means attackers are already using it. CISA's due date for federal agencies is November 24, 2026, and it is a sensible target for any business that runs Outlook on desktop computers.

What the flaw is

The National Vulnerability Database (NVD) describes it as a case where Outlook's user interface does not warn the user of unsafe actions, allowing an unauthorized attacker to perform spoofing over a network. CISA names it "Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability."

In plain terms, Outlook can fail to show a warning when a person is about to do something risky, so a spoofed message or request may look safer than it is. The record does not say which specific action is affected, and we are not going to guess.

Microsoft rates it 6.5 (medium) under CVSS 3.1. The vector shows it can be reached over the network, needs no account on the target, and requires the user to take an action. A medium score does not make it low priority: KEV listing is based on exploitation, not score. CISA's entry says it is unknown whether ransomware groups are using it.

Who is affected

The NVD record lists these products as vulnerable:

  • Microsoft 365 Apps for Enterprise (32-bit and 64-bit)
  • Office LTSC 2021: builds earlier than 16.0.14334.21048
  • Office LTSC 2024: builds earlier than 16.0.17932.21140

For Microsoft 365 Apps, the NVD record does not give a fixed build number. Microsoft's Office security releases page is the place to find it. We did not confirm which Outlook editions beyond those listed are affected, so treat Microsoft's information as the authority.

What CISA requires

CISA tells federal agencies to apply mitigations in accordance with vendor instructions, to follow BOD 26-04, and to stop using the product if mitigations are not available. CISA also asks organizations to assess each asset's internet exposure. Defense contractors and other regulated businesses often mirror CISA deadlines in their own policies, so it helps to have a date written down.

Checklist

  1. Find your Office versions. In Outlook, open File, then Office Account, then About Outlook. Note the build number on a few computers, or pull it from your management console if you have one.
  2. Open Microsoft's Office security releases page and write down the fixed build for each product you run.
  3. Update Office on every computer, including laptops that rarely connect to the office network and shared machines. Restart Outlook after the update so it takes effect.
  4. Compare builds. Any computer below the fixed build is still exposed. Check Office LTSC 2021 against 16.0.14334.21048 and Office LTSC 2024 against 16.0.17932.21140.
  5. Remind staff to verify unusual requests for payments, password resets, or file access by phone or in person using a number they already know, not one in the message.
  6. Record the date you finished. If you handle CUI or answer to an auditor, keep that note with your patch records.

What can wait

You do not need to replace Outlook, move to a different mail client, or rebuild your email setup. This is a patching job. Broader work, such as reviewing external-sender warnings in Microsoft 365 or tightening mail filtering, is worth doing but should not hold up the update.

How to check you are done

Every Office installation should report a build at or above the fixed one in Microsoft's advisory. If you cannot list builds across all computers, that gap is the real finding, and it is worth closing before the next flaw like this one.

When to get help

If you are not sure which Office products you run, or cannot confirm that every computer updated, our engineers can inventory and patch them through our managed IT services or review your exposure under cybersecurity. Reach us at contact us.

Sources

TaggedOutlookCISA KEVMicrosoft Officepatching

← All insights