Advisory

CVE-2026-124194: Microsoft Office Outlook Spoofing Flaw Actively Exploited (CISA KEV)

A missing user-interaction warning in Microsoft Office Outlook allows an unauthenticated, remote attacker to perform spoofing over a network without any safety prompt alerting the user. The vulnerability has been added to the CISA Known Exploited Vulnerabilities catalog, confirming active exploitation in the wild.

TL;DR: Apply Microsoft's mitigations immediately in line with CISA BOD 26-04 guidance; if no mitigation is available, discontinue use of the affected product. Verify your Outlook deployment is fully patched and monitor your external attack surface for exposed instances.

What Is the Vulnerability?

CVE-2026-124194 is classified under CWE-356 – Product UI Does Not Warn User of Unsafe Actions. In Microsoft Office Outlook, a critical safety prompt that should alert users before an unsafe action occurs is absent. Because users receive no warning, they can be manipulated into triggering a spoofing attack without any visible indication that something malicious is happening.

The National Vulnerability Database (NVD) describes it as follows: "Product UI does not warn user of unsafe actions in Microsoft Office Outlook, allowing an unauthorized attacker to perform spoofing over a network."

Key technical attributes from NVD:

  • CVSS 3.1 Score: 6.5 (MEDIUM)
  • Attack Vector: Network — the attacker does not need local or adjacent access.
  • Attack Complexity: Low — no special conditions are required.
  • Privileges Required: None — no authenticated session is needed by the attacker.
  • User Interaction: Required — the victim must perform some action, such as opening or previewing a crafted message.
  • Confidentiality Impact: High — successful exploitation can expose sensitive information.
  • Integrity / Availability Impact: None — per the CVSS vector, the vulnerability does not directly corrupt data or cause downtime.

Who and What Is Affected?

The affected product is Microsoft Office Outlook, as identified by the vendor (Microsoft) in both the NVD entry and the CISA Known Exploited Vulnerabilities (KEV) catalog. The advisory does not specify particular build numbers or versions beyond the product family, so all organizations running Microsoft Office Outlook should treat themselves as potentially affected until Microsoft's own advisory confirms otherwise.

Because the attack vector is Network and no privileges are required on the attacker's side, any Outlook deployment reachable over a network — including cloud-connected or internet-facing configurations — is in scope. Organizations with large numbers of Outlook users face a correspondingly broad attack surface given that user interaction (e.g., viewing a crafted email) is the only prerequisite.

  • Enterprise environments running Microsoft Office Outlook on-premises or hybrid.
  • Organizations using Outlook as part of a Microsoft 365 / Exchange Online deployment where email arrives from untrusted senders.
  • Government agencies subject to CISA Binding Operational Directive (BOD) 26-04 requirements.

What Is the Impact?

The primary impact recorded in NVD is spoofing: an unauthorized remote attacker can present falsified identity or content to Outlook users. Because the UI suppresses any safety warning, users have no native mechanism to detect that an unsafe action is being performed on their behalf.

The CVSS Confidentiality score is rated High, meaning successful exploitation can expose sensitive data accessible to or through the Outlook client. Integrity and Availability are scored as None in the base vector, though real-world exploitation chains may compound risks when combined with other vulnerabilities.

Critically, this vulnerability is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog (added 2026-11-10), which means CISA has confirmed evidence of active exploitation. Per CISA's KEV summary: "Microsoft Office Outlook contains a missing user interaction for potentially unsafe action vulnerability that allows an unauthorized attacker to perform spoofing over a network."

For U.S. federal civilian executive branch (FCEB) agencies, remediation is mandatory under BOD 26-04. All other organizations should treat KEV inclusion as a strong signal to prioritize this patch above lower-severity or non-exploited items.

What Should You Do Right Now?

CISA's required action for this KEV entry is clear:

  1. Apply vendor mitigations immediately. Follow Microsoft's own advisory and patch guidance. Ensure compliance with CISA BOD 26-04 patching timelines.
  2. Conduct forensic triage. CISA's KEV required action explicitly references "Forensics Triage Requirements." Review mail logs, Outlook activity, and any anomalous outbound connections that may indicate prior exploitation.
  3. Evaluate internet exposure. CISA instructs stakeholders to assess each asset's internet-facing status and apply BOD 26-04 patching guidelines accordingly. Cloud-hosted Outlook services have specific guidance under BOD 26-04.
  4. Discontinue use if mitigations are unavailable. If Microsoft has not yet released a patch or workaround applicable to your deployment, CISA's required action states the product should be discontinued until mitigations are available.
  5. Restrict untrusted email sources where possible. While not a substitute for patching, reducing exposure to untrusted or external senders can limit the opportunity for user interaction with malicious content.
  6. Monitor for indicators of spoofing activity. Alert on unexpected sender impersonation, unusual authentication events, and anomalous email behavior in your environment.

Primary references: CISA KEV Catalog | NVD – CVE-2026-124194 | Microsoft Security Response Center (MSRC) advisory for this CVE.

How Continuous External Testing Surfaces This Exposure

One of the core challenges with CVE-2026-124194 is visibility: an organization may not know which Outlook instances are externally reachable, unpatched, or running configurations that increase spoofing risk. Periodic, point-in-time assessments often miss the gap between patch release and patch deployment — a window that is especially dangerous for KEV-listed vulnerabilities with confirmed exploitation.

Continuous external attack surface monitoring addresses this by:

  • Enumerating internet-facing assets that run or interact with Outlook services, including those exposed via web interfaces, federation endpoints, or API integrations.
  • Detecting unpatched versions as soon as fingerprinting or behavioral signals indicate a vulnerable state, rather than waiting for a scheduled scan.
  • Alerting on configuration weaknesses — such as missing security headers or permissive sender policies — that lower the bar for spoofing attacks.
  • Providing audit evidence for BOD 26-04 compliance reporting, showing that your patching timelines meet the mandate.

Because the CVSS attack vector is Network and no privileges are required by the attacker, any internet-exposed Outlook touchpoint is a potential entry point that continuous external testing is specifically designed to find before an adversary does.

Sources & further reading: NVD CVE-2026-124194 and the CISA KEV catalog are the authority on affected and fixed versions. Vendor/independent analysis: msrc.microsoft.com, cisa.gov. This advisory contains no exploit code.

Frequently asked questions

Is CVE-2026-124194 being actively exploited?

Yes. CISA added CVE-2026-124194 to the Known Exploited Vulnerabilities (KEV) catalog on 2026-11-10, confirming active exploitation. Organizations should treat remediation as urgent and prioritize it in line with CISA BOD 26-04 requirements.

Do I need to be a U.S. federal agency for this to matter to my organization?

No. While BOD 26-04 is a binding mandate for U.S. federal civilian executive branch agencies, CISA KEV inclusion signals confirmed real-world exploitation that is relevant to any organization using Microsoft Office Outlook, regardless of sector or geography.

The CVSS score is only 6.5 (MEDIUM) — should I still prioritize this?

Yes. CVSS base scores measure theoretical severity under idealized conditions and do not account for active exploitation. KEV inclusion overrides the base score as a prioritization signal. A Medium-scored vulnerability with confirmed exploitation in the wild is more urgent than an unexploited Critical vulnerability in many risk frameworks.

What if Microsoft has not yet released a patch for my specific Outlook configuration?

CISA's required action states that if mitigations are unavailable, the product should be discontinued until they are. In the interim, reduce exposure by restricting untrusted email sources, reviewing CISA's forensic triage guidance, and monitoring closely for spoofing indicators.