> ## Content Index
> Fetch the complete content index at: https://f4n6.co.uk/llms.txt
> Use this file to discover other available public pages before exploring further.

# Outlook spoofing flaw CVE-2026-124194 added to CISA KEV
- URL: https://f4n6.co.uk/security-feed/outlook-spoofing-flaw-cve-2026-124194-added-to-cisa-kev/
- Published: 2026-11-10T22:02:52.000Z
- Updated: 2026-11-10T22:02:52.000Z
- Author: Jeff Davies
- Tags: #security-feed, CVE-2026-124194

## 1\. Executive summary

CVE-2026-124194, a spoofing vulnerability in Microsoft Office Outlook caused by a missing user interaction check for a potentially unsafe action, was published on 2026-11-10 and added to CISA KEV the same day. NVD scores it CVSS 6.5 MEDIUM (CWE-356). SecurityWeek reports that Microsoft is aware of active exploitation of this Outlook zero-day, which makes it the one item in this advisory that is confirmed exploited in the wild; the CISA KEV listing carries a remediation due date of 2026-11-24\. For EMEA financial services the exposure is mail-client side: Outlook is near-universal on trading, operations and treasury desktops, and a spoofing flaw that suppresses the user-interaction prompt is a phishing and business email compromise enabler rather than a code-execution path. The score is medium, but confirmed exploitation plus KEV status moves it above its CVSS band for prioritisation.

## 2\. Regulatory framing

| Article      | Trigger (the fact in this item)                                                                                                                                                                                                       | Practical impact                                                                                                                           |
| ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| DORA Art. 17 | CVE-2026-124194 is confirmed exploited in the wild (SecurityWeek) and sits in CISA KEV, so an exploitation attempt against an Outlook client is an ICT-related incident that must be handled through the incident management process. | Detection, triage and containment of Outlook spoofing attempts must run through the existing ICT incident process, with evidence retained. |
| DORA Art. 18 | Confirmed exploitation means an incident, if it occurs, needs classification against the major-incident criteria rather than being closed as a low-severity mail event on the strength of the 6.5 score.                              | Classification must weigh the exploitation state, not only CVSS; document the decision.                                                    |
| NIS2 Art. 23 | Where an entity in scope of NIS2 suffers an incident via this flaw, the reporting obligation to the competent authority and CSIRT is engaged.                                                                                         | Reporting timelines and thresholds apply once an incident is confirmed; pre-stage the notification content.                                |

## 3\. Technical analysis & attack chain

NVD describes CVE-2026-124194 as a missing user interaction for a potentially unsafe action vulnerability in Microsoft Office Outlook that allows an unauthorised attacker to perform spoofing over a network. The verified classification is CWE-356 (Product UI does not Warn of Dangerous Actions). In plain terms, the flaw is that Outlook fails to require or present the user-interaction step that would normally warn before a potentially unsafe action is taken, and an attacker can reach that condition remotely over the network.

The confirmed attack chain is short, because the public record is short:

1. An attacker delivers crafted content to an Outlook user over the network.
2. Outlook processes it without the user-interaction warning that CWE-356 describes as missing.
3. The result is spoofing: content is presented to the user as something it is not.

SecurityWeek states that Microsoft is aware of active exploitation of this Outlook zero-day. No source in this set describes the delivery mechanism, the crafted content, the targeted versions, or what the spoofing is used to achieve. Those are gaps in public reporting, not omissions in this advisory.

What is not established. No affected or fixed Outlook version, build number or KB is named in any source here. No initial-access vector beyond "over a network" is given. No payload, malware capability, persistence mechanism, command-and-control channel, lateral movement or data access is described. No attacker is named and no attribution is made by any source. CISA records known ransomware campaign use as Unknown, so there is no basis to link this to ransomware.

Severity note. The CVSS 6.5 MEDIUM rating and the CWE-356 classification are the verified values. The exploitation state (confirmed in the wild per SecurityWeek, KEV-listed per CISA) is what raises operational priority; the score itself does not.

Single-source caveat. The active-exploitation claim rests on SecurityWeek's report of Microsoft's awareness. It is corroborated in effect by the CISA KEV listing, which requires evidence of exploitation, but the underlying vendor statement is reported by one outlet in this set. Treat the exploitation state as established for prioritisation and verify against Microsoft's own advisory before any client communication that names it.

## 4\. Mitigation & containment

No fixed release is named in public reporting for CVE-2026-124194\. The CISA KEV entry directs defenders to apply mitigations in accordance with vendor instructions and to follow BOD 26-04 guidance, with a due date of 2026-11-24\. Because no patch identifier is available here, the steps below are containment and verification actions that do not depend on a version number.

### P1 (within 24 hours)

- Confirm the current Outlook build across the estate against Microsoft's advisory for CVE-2026-124194 and apply whatever update Microsoft names there; do not wait for a version number from this advisory, which does not carry one.
- Treat the CISA KEV due date of 2026-11-24 as the outer bound and aim to close before it.
- Hunt mail logs and endpoint telemetry for Outlook spoofing indicators over the past 30 days; the sources give no atomic indicators, so hunt on behaviour (see §5).

### P2 (within 72 hours)

- Review mail-flow rules and external-sender marking so that spoofed content reaching Outlook is flagged at the gateway as well as the client; the client-side warning is the control this CVE removes.
- Confirm that users who received suspicious mail in the hunt window are identified and their mailbox activity reviewed for follow-on credential or payment-fraud attempts.

### P3 (within 7 days)

- Add the behaviour in §5 to detection content and confirm alerting fires.
- Record the CVE, the exploitation state and the KEV due date in the vulnerability register with the medium score and the exploitation override noted.

## 5\. Indicators of compromise

No indicators of compromise available in the source material. No hashes, domains, IP addresses, file paths or command lines are given for CVE-2026-124194 in any source provided.

The sources describe observable behaviour but no atomic indicators, so the following behavioural indicators are offered for hunting. They are inferences from the CWE-356 mechanism and the spoofing description, not artefacts copied from a report; confidence is correspondingly low and they should be tuned before enforcement.

### Behavioural indicators

| behaviour                                                                                                       | where to observe                                                    | confidence                                            |
| --------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------- | ----------------------------------------------------- |
| Outlook presents content as trusted or expected without the user-interaction warning that would normally appear | Outlook client telemetry, user reports of unexpected mail rendering | low (inferred from CWE-356)                           |
| Inbound mail crafted to trigger the missing-warning condition reaches users over the network                    | Mail gateway logs, message trace                                    | low (inferred from the network spoofing description)  |
| Follow-on user action after a spoofed message (credential entry, payment change)                                | Identity logs, payment-change requests                              | low (inferred; no source describes post-exploitation) |

## 6\. Detection

Insufficient indicators to author detection rules. The sources give no strings, command lines, file names, registry keys or network artefacts for CVE-2026-124194, and the behavioural description in §5 is too generic to build a rule that would not fire on ordinary mail traffic. Detection should be built once Microsoft's advisory for this CVE is obtained and its specifics are available.

## CVE assessment

1 referenced CVE — **1 actively exploited (CISA KEV)**

| CVE                                                                                | CVSS       | Exploited        | EPSS | Summary                                                                                                                          |
| ---------------------------------------------------------------------------------- | ---------- | ---------------- | ---- | -------------------------------------------------------------------------------------------------------------------------------- |
| [CVE-2026-124194](https://nvd.nist.gov/vuln/detail/CVE-2026-124194?ref=f4n6.co.uk) | 6.5 Medium | ⚠ KEV 2026-11-10 | —    | Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing… |

## 7\. Sources

- NVD, CVE-2026-124194 detail, https://nvd.nist.gov/vuln/detail/CVE-2026-124194, published 2026-11-10
- SecurityWeek, Exploited Outlook Zero-Day Among 1,094 Flaws Patched by Microsoft, https://www.securityweek.com/exploited-outlook-zero-day-among-1094-flaws-patched-by-microsoft/

The following related sources describe different SharePoint vulnerabilities and events and contribute no facts to this advisory: The Register (CVE-2026-45659), SecurityWeek (CVE-2026-65660), The Hacker News (CVE-2026-58644 and CVE-2026-45659), and Tenable Research (CVE-2026-32201, CVE-2026-45659, CVE-2026-56164, CVE-2026-55040, CVE-2026-58644).

## 8\. Adverse Trace position

Adverse Trace assesses CVE-2026-124194 as medium severity on the verified CVSS 6.5, raised in operational priority by confirmed exploitation and CISA KEV status with a 2026-11-24 due date. The client impact for EMEA financial services is a mail-client spoofing exposure that supports phishing and payment-fraud attempts rather than direct code execution; the absence of a named fixed version in public reporting is the main constraint on remediation, and the exploitation claim is single-sourced to SecurityWeek's report of Microsoft's statement, so we will verify it against Microsoft's advisory before any client-facing attribution of exploitation. We will obtain Microsoft's advisory for the affected and fixed Outlook builds, re-issue this note with a patch identifier and any atomic indicators once available, and track the KEV due date against client patch status.

---

[Read the original source →](https://nvd.nist.gov/vuln/detail/CVE-2026-124194?ref=f4n6.co.uk)

*Published via PulseTrace — Adverse Trace threat intelligence.*