skulldc

CISA lists Microsoft Outlook spoofing flaw CVE-2026-124194 as exploited

Outlook fails to warn users before a potentially unsafe action, letting an unauthorized attacker perform spoofing over a network; CISA added it to KEV on 2026-11-10.

What CISA added

On 2026-11-10 CISA added CVE-2026-124194 to its catalog of known exploited vulnerabilities (KEV), the list of flaws the agency tracks as exploited in the wild. The entry is named “Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability”. It lists the vendor as Microsoft, the product as Office, and the weakness as CWE-356. Known ransomware campaign use is listed as Unknown. For US federal civilian agencies bound by BOD 22-01, the due date is 2026-11-24.

What the flaw is

The KEV description says Microsoft Office Outlook contains a missing user interaction for potentially unsafe action vulnerability that lets an unauthorized attacker perform spoofing over a network. The NVD record, published on 2026-11-10 and already in the status Analyzed, describes the same problem from the interface side: the product UI does not warn the user of unsafe actions in Microsoft Office Outlook.

Put together, the two records describe a missing safety prompt. Outlook goes ahead with an action that should have asked the user first, and an attacker can use that gap to make something look like it comes from a source it does not come from. Neither record says which action is affected, what exactly can be spoofed, or which Outlook builds are vulnerable. Those details sit with the vendor.

Severity

NVD shows a secondary CVSS 3.1 base score of 6.5 MEDIUM, assigned by Microsoft, with the vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. In plain terms: the attack works over the network, complexity is low, no privileges are needed, user interaction is required, and the scope is unchanged. Impact on confidentiality is rated high, while integrity and availability are rated as not affected.

Two parts of that vector are worth reading closely. UI:R means the scoring assumes a victim still has to do something, which fits a spoofing attack where a recipient acts on a message they have been misled about. And the split between high confidentiality impact and no integrity impact points to exposure of information as the expected outcome, not changes to data or systems.

A medium base score next to a KEV listing is not a contradiction. CVSS rates a flaw in isolation, while the KEV entry records that attackers are already using it, and a flaw that needs a user to act can still be exploited at scale through mail.

What to do

The KEV required action is to apply mitigations in accordance with vendor instructions, following CISA’s BOD 26-04 guidance on prioritizing security updates based on risk and its “Forensics Triage Requirements”. For cloud services, the same BOD 26-04 guidance applies; if mitigations are unavailable, use of the product should be discontinued. Stakeholders are asked to evaluate each asset’s internet exposure.

The vendor guidance is Microsoft’s update guide entry for CVE-2026-124194 on msrc.microsoft.com, which the KEV notes and the NVD references both point to. Because neither public record lists affected or fixed versions, that entry is the place to confirm which Outlook installations need the update. Administrators should check that the update has reached every Outlook installation they manage, and, since exploitation depends on a user acting, keep users aware that a message that looks routine can still be spoofed.


Source: CVE-2026-124194 (NVD, CISA KEV)