home / blog
2026-11-11 · medium
CVE-2026-124194: Spoofing and NTLM leak in Outlook
Microsoft Outlook: UI does not protect from unsafe actions. Spoofing and NTLM leak over network. CVSS 6.5.

CVE-2026-124194 is a UI deficiency in Microsoft Outlook that fails to warn users of unsafe actions. Unauthorized attackers can perform spoofing and force NTLM authentication over the network, compromising user credentials. The vulnerability directly impacts IT administrators and security teams managing Outlook environments, where spoofing remains a primary attack vector. Network access is the only requirement.
CVSS 6.5 (medium severity), but real damage depends on data sensitivity in Outlook. The CVE was published on November 10; PoC repositories appeared on GitHub the next day (explicitly untested). This timing suggests rapid research community response. Signals are coherent and verifiable between NVD and GitHub. No active exploitation in the wild has been reported.
Defense actions: 1) Monitor Microsoft's patch status and plan deployment. 2) Inspect Outlook logs for spoofing or anomalous authentication. 3) Communicate to users to verify unexpected authentication requests. 4) Implement MFA to mitigate NTLM credential leaks. 5) Review Exchange configuration to limit legacy protocols. Contact Microsoft Security Response Center for personalized guidance.
At a glance
- What
- The UI of Microsoft Office Outlook does not warn users of unsafe actions, allowing an unauthorized attacker to perform spoofing over a network. CVE-2026-124194 also involves NTLM credential leak through forced authentication.
- Severity
- CVSS 6.5 (medium). The score reflects network access, no authentication required, and impact on credential confidentiality.
- Affected versions
- Not reported in official NVD documentation. Check with Microsoft vendor for specific impacts.
- Fix
- According to GitHub signals, a patch has been available since November 2026 ('patched 2026-11'). Specific details not reported. Contact Microsoft Security Response Center for official guidance.
- Status
- CVE published on 2026-11-10. Unverified proof of concept available on GitHub repositories as of 2026-11-11. No reports of active exploitation in production environments.
- Action
- 1) Monitor Microsoft's patch status and plan deployment. 2) Inspect Outlook logs for signs of spoofing or anomalous authentication. 3) Communicate to users to watch for unexpected authentication requests. 4) Implement MFA to mitigate the impact of NTLM credential leaks.
Sources: NVD, CVE-2026-124194