On this page (7 sections)

Microsoft's November 2026 Patch Tuesday includes a fix for CVE-2026-124194, a Microsoft Outlook spoofing vulnerability that Microsoft says has been exploited. SecurityWeek reports that the flaw lets a specially crafted message file make Outlook reach out to an attacker-controlled location without the usual external-content warning.

If you or your staff use Microsoft 365 Apps for Enterprise, Office LTSC 2021 or Office LTSC 2024, this one should go to the front of the patching queue. The CVSS score is moderate, but active exploitation and a credential-related impact change the priority.

What happened

On 2026-11-10, Microsoft released its monthly security updates. According to SecurityWeek, the release fixes 1,094 vulnerabilities, and CVE-2026-124194 is the one Microsoft flagged as exploited. The CVE data also shows the flaw was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on the same day, with a remediation due date of 2026-11-24 for the agencies the directive covers. The KEV entry lists ransomware use as unknown.

Microsoft's advisory gives no information about the attacks that were observed, so who is behind them, how widespread they are and who was targeted are all unconfirmed. SecurityWeek also reports the bug was not publicly disclosed before the fix was released.

Technical details

The NVD entry describes the issue as a missing user interaction for a potentially unsafe action in Outlook, which allows an unauthorized attacker to perform spoofing over a network. In plain terms, Outlook is supposed to warn you before it loads content from an external location. Here, that warning can be skipped.

Microsoft's description, quoted by SecurityWeek, says an attacker could send a crafted message file and convince a user to open it. Opening it could make Outlook connect to an attacker-controlled network location without the usual external-content warning. Microsoft states that this discloses the user's NTLMv2 hash, which the attacker could use to authenticate as that user.

Two details matter for risk assessment:

  • The user has to be tricked into opening the file. Microsoft says the flaw cannot be triggered through the Preview Pane, so merely selecting the message in the reading pane is not the trigger.
  • What leaks is an NTLMv2 hash, not a plain-text password. The hash can still be abused to authenticate as the user, as Microsoft describes, which is why exposure of it is treated seriously.
The sources only say "a specially crafted message file". They do not name the file format. Outlook message files (.msg) are a plausible candidate, but that is an assumption, not something Microsoft or the other sources confirm.

Who is affected

Microsoft's advisory, as relayed by SecurityWeek, lists Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024 as affected. The sources do not say whether other Office editions are affected, so check the Microsoft advisory for your exact product.

Realistic exposure is highest for organizations where staff open message files received from outside, such as support desks, finance teams, recruiters and agencies handling client attachments. If you run Windows domain accounts, a leaked hash is tied to a real identity on your network.

How to check your exposure

Start by finding out which Office builds your users run and whether the November 2026 update has reached them. In Outlook, open File, then Office Account, and look at the product name and version information. The sources do not list fixed build numbers, so compare against the build given in the Microsoft advisory for your update channel.

For administrators, review inventory or update-management reports for machines running the three affected products and flag any that have not installed the November updates. You can also review mail gateway and mailbox logs for unusual message-file attachments from external senders in recent weeks, since Microsoft describes delivery as a crafted message file sent to the victim. Because the sources do not name the file type (Outlook .msg files are a likely but unconfirmed candidate) and Microsoft has not published indicators of compromise, treat this as a hunting hint rather than a confirmed indicator.

What to do now

  1. Install the November 2026 Microsoft Office updates on all machines running Microsoft 365 Apps for Enterprise, Office LTSC 2021 or Office LTSC 2024, and confirm the install through your update tooling.
  2. Prioritize systems used by people who regularly open external attachments, and do not wait for the next routine patch cycle.
  3. Warn staff not to open unexpected message files from outside the organization, even if the sender looks familiar.
  4. Consider filtering or quarantining external message-file attachments (for example Outlook .msg files, though the format is unconfirmed) at the mail gateway until patching is confirmed.
  5. As general hardening, not specific to this advisory, block outbound NTLM-capable traffic such as SMB (TCP 445) to the internet at your perimeter, so a connection to an external host cannot complete.
  6. If you suspect someone opened a suspicious message file, reset that user's password and review their sign-in activity for unusual authentication.
  7. If you are subject to CISA's directive, follow the KEV remediation due date of 2026-11-24.
Caution. Resetting passwords and changing perimeter rules can interrupt users and services. Test egress filtering changes on a small group first and tell affected staff before forcing resets.

Detection and monitoring

Because Microsoft has shared no indicators, monitoring has to be behavioral. Watch for Outlook processes making outbound connections to unfamiliar external hosts, and for authentication attempts from unexpected locations using accounts of users who recently received external message files. Alert on logins that succeed from new IP addresses shortly after such emails.

Keep an eye on the NVD record and Microsoft's advisory for updates, as details about the observed attacks may be added later. If you also run public web properties, keeping them monitored for certificate, DNS and header changes with a tool such as Webforta Monitor helps you spot unrelated drift while your team is busy patching.

Context: a large Patch Tuesday

This is one item in a very large release. SecurityWeek reports Windows accounted for 726 of the fixes and Office for 174, and that these are the final monthly security updates for Windows 11 version 23H2 Enterprise and Education editions. If you manage a mixed estate, use the same maintenance window to review other pending updates. For general guidance on keeping small organizations current, see our small business website security guide.

Sources

This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.

  1. Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability (CVE-2026-124194) is being actively exploitednvd.nist.gov ·
  2. Exploited Outlook Zero-Day Among 1,094 Flaws Patched by Microsoftsecurityweek.com ·
  • Outlook
  • Microsoft
  • Patch Tuesday
  • CISA KEV
  • NTLM
  • Zero-day