
CVE-2026-124194: Outlook's "Medium" Spoofing Bug Is on CISA's KEV List With a 14-Day Clock
Microsoft rates it 6.5. The CVE record's own temporal metrics already say E:H — exploit code maturity: High. Here's what's affected and what to do before November 24.
CVE Tools4 min read
Overview
CVE-2026-124194 is a spoofing vulnerability in Microsoft Outlook for Windows, patched in the November 2026 Patch Tuesday release and added to CISA's Known Exploited Vulnerabilities (KEV) catalog the same day. Microsoft's own description: the Outlook UI "does not warn user of unsafe actions," letting an unauthenticated attacker over a network trigger spoofing — in practice, a forced-authentication flow that leaks the victim's NetNTLMv2 hash to an attacker-controlled server once a specially crafted message item is opened.
Scores as of 2026-11-12live record →
| Product | Affected versions | Fix |
|---|---|---|
| Microsoft 365 Apps for Enterprise (32-bit / x64) | 16.0.1 and later, pre-update | Current Channel auto-update via aka.ms/OfficeSecurityReleases |
| Microsoft Office LTSC 2021 (32-bit / x64) | 16.0.1 up to (not including) 16.0.14334.21048 | Update to 16.0.14334.21048 or later |
| Microsoft Office LTSC 2024 (32-bit / x64) | 16.0.0 up to (not including) 16.0.17932.21140 | Update to 16.0.17932.21140 or later |
Why the score and the catalog disagree
CVE-2026-124194 is the latest in a lineage that starts with CVE-2023-23397, the Outlook calendar-reminder bug APT28 used against European government and military targets in 2022–2023. Both bugs are the same primitive — Outlook dereferencing a remote path and leaking the current user's NTLM hash — but they score nothing alike, and the gap is entirely about user interaction, not actual risk.
Two Outlook NTLM-leak bugs, three years apart
- CVSS 9.8 — Critical
- UI:N — zero user interaction; a calendar reminder fires automatically
- Full confidentiality + integrity + availability impact in the vector
- Attributed to APT28 / Fancy Bear in nation-state espionage
- CVSS 6.5 — Medium
- UI:R — victim must open the crafted item (not merely preview it)
- Confidentiality-only impact in the vector; no integrity or availability credit
- No attribution published by Microsoft or CISA as of this writing
Scores as of 2026-11-12live record →
CVE-2026-124194's first two days
- Microsoft ships the fixPart of November Patch Tuesday. Rated 6.5/Medium. The published record carries CVSS temporal metrics E:H (Exploit Code Maturity: High) and RC:C (Report Confidence: Confirmed).
- CISA adds it to KEV the same daySSVC exploitation status: active. Federal civilian agencies given until 2026-11-24 under BOD 26-04.
- Coverage acceleratesMultiple security outlets publish within hours, most drawing the direct comparison to CVE-2023-23397.
Mitigation guidance
- Update Microsoft 365 Apps for Enterprise to the latest Current Channel build, or confirm auto-update already applied it.
- Update Office LTSC 2021 to 16.0.14334.21048 or later, and Office LTSC 2024 to 16.0.17932.21140 or later — LTSC does not auto-update on the same cadence as 365 Apps.
- There is no published workaround. Our own remediation data for this CVE shows has_workaround: false — the update is the only fix Microsoft has offered.
- As general hygiene against this whole bug class: enforce SMB signing and restrict outbound SMB (445) / WebDAV to untrusted hosts at the network egress, since forced-NTLM-authentication bugs are only valuable to an attacker if the leaked hash can reach them or be relayed.
What this means for your fleet
If you're triaging by CVSS alone, this bug sorts below dozens of patched-but-not-exploited bugs in the same release. That ordering is backwards for anything already in KEV: CISA's catalog is a confirmed-exploitation list, not a severity list, and it has repeatedly carried sub-7.0 bugs — we covered the same pattern in SharePoint's 5.3 that isn't in July. Triage by exploitation status first, CVSS second. Outlook desktop clients fitting the affected-version table above should move to the front of this week's patch queue, Preview Pane habits notwithstanding — Microsoft's advisory language specifically ties this to opening the item, not previewing it, but that distinction is worth verifying against your own build rather than assuming the user's workflow matches the FAQ.
Is CVE-2026-124194 the same bug as CVE-2023-23397?
Does this affect Outlook on the web, Mac, iOS or Android?
Is there a temporary workaround if I can't patch immediately?
Why is the EPSS score so low for a KEV-listed bug?
Data as of 2026-11-12live record →
Sources: Microsoft Security Response Center advisory for CVE-2026-124194, CISA Known Exploited Vulnerabilities catalog, CVE.org record, NVD entry.