CVE-2026-124194
Microsoft 365 Apps
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-124194 is a medium-severity Product UI does not Warn User of Unsafe Actions (CWE-356) vulnerability in Microsoft 365 Apps. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Subvert Trust Controls (T1553); ranked in the top 24% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities catalog.
Advisories
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-122310
Vulnerability Data
Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing over a network.
- CWE(s)
- KEV Date Added
- 10 November 2026
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Mandates explicit user-visible indication, directly countering absence of warnings for device activation.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices include UI design requirements that warn users before unsafe actions.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can verify presence of warnings for unsafe user actions.
Security awareness training can teach users to heed or demand warnings for unsafe actions.
Secure coding practices can embed user warnings before unsafe operations.
A.8.30 carries its effect through contractual requirements for secure design, coding and testing (8.25–8.29), which reach a UI-warning weakness in outsourced software the same way they reach other ordinary software CWEs; the clause's declared ceiling on this verb is `partial`, and the remainder is the fallibility of the supplier's design practice and the slice of UI-warning decisions not covered by security-focused design guidance.
A.8.7's malware detection and repair software, scanning files and email attachments before use (items f.1, f.2), blocks exploitation of CWE-356 in the subset of cases where the unsafe action involves malware (e.g., executing a malicious attachment, opening a macro-laden document), but CWE-356 also covers non-malware unsafe actions such as certificate-acceptance warnings and setuid extraction warnings, which A.8.7 does not reach.