Outlook Zero-Day CVE-2026-124194: Opening a Message File Can Hand Over Your Windows Login
Bit4Bit DFIR, practical notes for people who actually run the systems.
Microsoft's November 2026 Patch Tuesday, released November 10, fixed about 1,094 flaws, 63 of them rated Critical. Only one was already being exploited in the wild, and it is the one most people will miss, because it is rated Moderate and it does not come through Windows Update at all.
The flaw is CVE-2026-124194, a Microsoft Outlook spoofing vulnerability. It is rated Moderate with a CVSS 3.1 score of 6.5, and Microsoft marks it as Exploitation Detected. An attacker sends a specially crafted message file and persuades the target to open it in Outlook. At that point Outlook can connect to a network location the attacker controls without showing the warning it would normally show for external content. That quiet connection discloses the user's NTLMv2 hash, and Microsoft says the attacker could use it to authenticate as the user.
On November 10, CISA added CVE-2026-124194 to the Known Exploited Vulnerabilities catalog, with a fix deadline of November 24, 2026 for US federal civilian agencies.
What is actually affected
- Microsoft 365 Apps for Enterprise
- Microsoft Office LTSC 2024
- Microsoft Office LTSC 2021
Both 32-bit and 64-bit editions are affected. The Preview Pane is not an attack vector: simply seeing a message in the inbox list or reading pane does not trigger it. The user has to actually open the malicious message file.
That last detail matters for triage. This is not a zero-click worm. It needs a user to open a file, which means email gateway filtering and user awareness still buy real protection while patching is under way. It also means the risk concentrates on people who routinely open message files sent from outside, such as shared .msg files from clients, vendors, or casework.
Why a Moderate rating still deserves urgent attention
A CVSS 6.5 looks easy to deprioritise next to the 63 Critical flaws in the same release. The exploited status is what changes the maths. An exploited Moderate bug is a bigger real-world risk than a Critical bug that only exists in theory, and Microsoft's advisory says this one was not publicly disclosed before the fix shipped, which usually means someone found it being used in real attacks rather than reading about it in a research paper.
The exposed credential is an NTLMv2 hash. That is a piece of Windows sign-in data, not a plaintext password, but it is enough for an attacker to authenticate as the user on other systems, typically by relaying it, or to try cracking it offline to recover the password. One opened file can therefore turn into lateral movement, not just a single compromised mailbox.
Microsoft credits the discovery in part to a researcher working with Anthropic's Claude, alongside a researcher who goes by "nono" and security researcher Benoit Sevens.
The patch trap: Windows Update does not fix this
This is the detail most likely to catch a team out. The Outlook fix is delivered through Office's own updater, not through Windows Update. Installing the Windows cumulative update and restarting does nothing for this bug.
Update Office first, from inside an Office app: File > Account > Update Options > Update Now, in Outlook or Word. Then install the Windows updates as well.
On the Windows side, the November cumulative update KB5132061 also enables NTLM clients to offer message signing by default for non-anonymous connections. Microsoft says that change helps reduce exposure to NTLM relay attacks, which is the same attack class this Outlook flaw feeds into. It is worth taking, but it is not a substitute for the Office update.
What to do
If you run Microsoft 365 Apps or Office LTSC 2021/2024 on Windows:
- Update Office now, using File > Account > Update Options > Update Now. Confirm the build is at or past the November 10 security release.
- Install the November Windows cumulative update (KB5132061 for Windows 11 24H2/25H2/26H2) and restart.
- Until patching is done, treat unexpected .msg files and message-file attachments from outside the organisation as suspect, and remind users not to open them on request. Your email gateway is your best control in the meantime.
If you only use Outlook on the web, Outlook for Mac, or the Outlook mobile apps, this CVE is not on Microsoft's affected list for those clients, so no action is needed for this flaw. Check your Windows desktop installs instead, since those are the ones in scope.
The DFIR angle
If you have Windows users on affected Office builds, check for signs the hash already left the building:
- Look for Outlook opening .msg or message files from external senders, especially around November 10 and earlier, and for Outlook making outbound connections to unfamiliar external SMB or WebDAV locations.
- Review authentication logs for unexpected NTLM authentications, logons from hosts the user does not normally use, and lateral movement shortly after a suspicious message file was opened.
- Treat any NTLM relay or pass-the-hash activity tied to an affected user as potentially seeded by this flaw, and rotate or reset credentials for users who opened a suspect file, rather than only patching the endpoint.
- Remember that patching closes the hole, it does not undo a hash that was already disclosed. If the timeline shows exposure before the fix was installed, investigate the activity that occurred before the patch, not just the patched state.
The lesson here is a familiar one: the bug that gets exploited is not always the one with the highest score. It is the one with a working attack, a quiet trigger, and a patch delivered through a channel nobody checks. Update Office, then check whether anyone already opened the file.
Sources: Microsoft Security Update Guide entry for CVE-2026-124194 and November 2026 Office security release notes; CISA Known Exploited Vulnerabilities catalog (added November 10, 2026, due November 24, 2026); CSO Online and Tenable breakdowns of the November 2026 Patch Tuesday release (about 1,094 flaws, 63 Critical). Counts differ slightly by source; the exploited Outlook flaw and its CVSS 6.5 rating are consistent across them.
Top comments (0)