On November 10, CISA put CVE-2026-124194 on its Known Exploited Vulnerabilities list. The flaw affects Microsoft Office Outlook: a missing Outlook warning for a potentially unsafe action allows network spoofing. Organizations running the affected desktop Office editions have a November 24 action date in CISA’s entry.
The Microsoft-authored CVE record names Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024 on 32-bit and x64 systems. Inventory those editions and architectures on managed endpoints.
Outlook misses a safety warning
Microsoft describes the weakness as “Product ui does not warn user of unsafe actions” and classifies it as CWE-356. Its severity vector rates network attack with no attacker privileges and user interaction required. The scored attack requires a user action; include that prerequisite when warning Outlook users. Microsoft describes the outcome as spoofing over a network.
CISA’s KEV listing establishes exploitation. Microsoft scores the issue 6.5, or medium severity, in its CVSS 3.1 record. The KEV listing makes deployment urgent despite the medium CVSS score. The NVD record carries the same three affected product families and user-interaction requirement.
The edition determines the version check
For Office LTSC 2021, Microsoft lists versions before 16.0.14334.21048 as affected. For Office LTSC 2024, it lists versions before 16.0.17932.21140. Check the installed Office build on those endpoints, then apply Microsoft’s applicable Outlook security update through the organization’s normal servicing path. The version bounds are useful for triage; confirm the update actually installed before treating an endpoint as remediated.
Microsoft 365 uses channel-specific updates. For Microsoft 365 Apps for Enterprise, Microsoft’s CVE record directs administrators to Office security releases for their update channel; it lists no numeric end version for this edition. Compare each installed build with the Microsoft security release guidance for its update channel before marking an endpoint updated.
Match Outlook installs to updates
Start with endpoint inventory for those three Office families, including 32-bit and x64 installs. Prioritize endpoints below the two LTSC version bounds and compare Microsoft 365 Apps deployments against their own channel guidance. Roll out the relevant vendor update and retain the installed-build result from the endpoint management system as verification. CISA directs affected organizations to apply vendor mitigations and evaluate each asset’s internet exposure under its November 24 action schedule.
These records contain no exploitation indicator or dependable mail-log pattern for a targeted search. Investigate suspicious Outlook activity through the normal incident-response queue; verify remediation against each endpoint’s installed build and the applicable Microsoft update. Keep unresolved endpoints assigned and scheduled.