Outlook already exploited: opening a message file can hand over the Windows credential
Microsoft marked CVE-2026-124194 as exploited on Nov. 10, 2026. In desktop Outlook, opening a file can reveal the NTLMv2 hash without the external-content warning. What a small business checks today.
A file arrives by email and asks to be opened in Outlook. If someone opens it, the program can connect to a server belonging to the sender, without the usual external-content warning, and hand over a Windows credential: the NTLMv2 hash. Microsoft published the fix on November 10, 2026, as CVE-2026-124194, and records the flaw as already exploited.
For a small or mid-sized business, the practical point is this. The Windows update on the PC does not stand in for the Office update. Anyone who uses desktop Outlook checks the program’s build, not only the Windows build.
What Microsoft described
The flaw is classified as spoofing, with a moderate severity and a CVSS 3.1 score of 6.5. In the update guide, Microsoft marks exploitation as detected. The same record says the flaw had not been publicly disclosed before the fix.
Microsoft’s text, in the CVE questions, describes the path:
- An unauthenticated attacker sends a specially crafted message file and convinces someone to open it in an affected version of Outlook.
- Opening the file can cause Outlook to connect to an attacker-controlled network location without the usual external-content warning.
- That connection can disclose authentication information that could be used to impersonate the user.
- Exploitation requires network connectivity and an action by the person.
- The Preview Pane is not an attack vector.
- The interaction Microsoft describes is opening a malicious Office file.
- On the confidentiality metric, Microsoft explains the effect: the flaw discloses the user’s NTLMv2 hash, and the attacker who receives it could use it to authenticate as that user.
SecurityWeek, on November 10, noted that Microsoft’s advisory gives no detail on the attacks already observed. The report treats the case as a zero-day: exploitation was already underway when the fix shipped.
What this means for the person who opens the company’s mail
The NTLMv2 hash is not the password typed on the screen. It is the credential Windows can accept to authenticate that account. Microsoft says an attacker could use it to authenticate as the user. The advisory does not give a count of companies hit, a sum of money, or a sector.
The concrete risks, from what Microsoft describes:
- Whoever opens the file in desktop Outlook can hand over a credential for their own account, if the version does not yet have the fix and the PC has network access.
- The warning the team learned to expect may not appear. The path described is the connection without the external-content warning.
- Reading the message in the Preview Pane is not the step Microsoft describes. The step is opening the file.
- The sender’s name does not prove the file. Microsoft says the attacker has to convince the person to open it.
- The fix already exists. In a small company, what is left is for it to be on the Outlook of every PC.
CISA added CVE-2026-124194 to its Known Exploited Vulnerabilities catalog on November 10, 2026, with a remediation date of November 24, 2026. The alert from the same day says Binding Operational Directive 26-04 applies to U.S. federal civilian executive branch agencies, and that CISA encourages every organization to prioritize flaws in that catalog. November 24 is the date in the U.S. catalog. It is not a legal deadline in Brazil or the rest of Latin America. For a small business here, the useful fact is the other one: the flaw is already in use, and the fix is already out.
In that catalog, use in a ransomware campaign is marked unknown. This article does not turn that into a ransomware case.
Which products Microsoft lists
In the CVE record, the affected products, with a fix published and customer action required, are:
- Microsoft 365 Apps for Enterprise, 32-bit and 64-bit
- Microsoft Office LTSC 2024, 32-bit and 64-bit, fixed build 16.0.17932.21140
- Microsoft Office LTSC 2021, 32-bit and 64-bit, fixed build 16.0.14334.21048
The Office security release notes for November 10, 2026 include CVE-2026-124194 in that day’s Outlook list. The page says those notes apply to Microsoft 365 Apps for enterprise, Microsoft 365 Apps for business, Office 2019, Office LTSC 2021, Office 2021, Office LTSC 2024, and Office 2024. The same page records that support for Office 2019 ended on October 14, 2025. The CVE record itself names only Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024. A company on a Business plan, or on retail Office, checks the build the same way: that day’s note publishes the channel package, and the comparison is against that line.
For the channel most small companies leave on automatic update, Current Channel, the note lists Version 2610 (Build 20527.20196). Retail Office 2024 and retail Office 2021 appear with the same Version 2610 (Build 20527.20196). Volume-licensed Office LTSC 2024 appears as Version 2408 (Build 17932.21140). Volume-licensed Office LTSC 2021 appears as Version 2108 (Build 14334.21048).
Monthly Enterprise Channel and Semi-Annual Enterprise Channel have other builds in the same note. The number to compare is the line for the company’s channel.
Outlook on the web and the mobile app do not appear on the affected-product list for this CVE. The risk Microsoft describes is opening the file in desktop Outlook.
How to check it on the PC
Malwarebytes, on November 11, separates the two updates. The Windows package is not the Office package. The path it describes for Office:
- Open an Office application, such as Word. In Outlook, the account may appear as Office Account.
- Go to File > Account.
- Under Product Information, select Update Options > Update Now.
- If the button is missing, select Enable Updates first. If the update controls do not appear on a company PC, updates may be managed centrally. The next step is to talk to whoever administers those PCs.
After the update, in File > Office Account > About Outlook, the version and build need to match the channel line in the November 10 notes. On Current Channel, that line is Version 2610 (Build 20527.20196). A build older than the one in the note does not yet have that day’s package.
Until the build is on every PC that opens Outlook, the note to the team fits in one sentence. A message file or an Office file the person was not expecting does not get opened in desktop Outlook, even when the sender looks familiar. The Preview Pane does not replace that rule: Microsoft says it does not trigger this flaw, and that opening the file does. An external-content warning that never appeared is also not proof the file is clean. In this flaw, the missing warning is part of the problem.
The November package, for anyone who still runs Exchange
Computerworld, on November 13, 2026, puts Outlook at the top of the Patch Tuesday list and records two separate points for anyone who still runs a server.
The first is the fix for the October problem on on-premises Exchange. The November Windows Server updates Computerworld cites for that are KB5131080 (Windows Server 2025), KB5131090 (2022), KB5131085 (2019), and KB5131291 (2016). This blog’s piece on the October update describes the symptom: Outlook on the web sign-in failing and messages stuck in the Outbox. Computerworld says the November package closes that case.
The second is what remains for Exchange 2016 and 2019. Computerworld reports Microsoft’s note this month: anyone still using those versions should consider them permanently vulnerable and upgrade the organization. The Exchange package cited in the same report is the one for Subscription Edition, KB5133453. That report does not include an update for Exchange 2016 or 2019.
There is also a different flaw, CVE-2026-116928, in the Windows Search component, with a CVSS score of 9.8. Malwarebytes and Computerworld describe a path in which Exchange Server indexes a crafted attachment without anyone opening the email. Malwarebytes notes that Microsoft has not reported exploitation of that flaw. It is not the Outlook CVE. It matters for a company that still runs Exchange on its own server. A company that uses only Exchange Online, inside Microsoft 365, is outside that on-premises indexing path.
SecurityWeek counted 1,094 flaws fixed in the November package. Computerworld, on November 13, reached 1,240 by adding 165 republished Chromium fixes and leaving out 19 Azure and open-source entries, starting from Microsoft’s 1,094. The two numbers describe different counts. The first item for a small business remains the Outlook flaw Microsoft already marks as exploited.
Frequently asked questions
What is CVE-2026-124194?
It is a spoofing flaw in Microsoft Outlook, rated moderate, with a CVSS 3.1 score of 6.5. Opening a specially crafted message file, in an affected version, can cause Outlook to connect to an attacker’s server without the external-content warning and disclose the user’s NTLMv2 hash. Microsoft published the fix on November 10, 2026, and marks the flaw as exploited.
Does the Preview Pane trigger this flaw?
Microsoft says the Preview Pane is not an attack vector. The step it describes is the person opening the file.
Does updating Windows cover this flaw?
The fix for this flaw ships through Office. Malwarebytes describes the path under File > Account > Update Options > Update Now, and the build check in About Outlook.
Does CISA’s November 24 date apply to a company in Latin America?
The date is in the U.S. known-exploited-vulnerabilities catalog, on the entry for this CVE. The directive CISA cites in the November 10 alert applies to U.S. federal civilian agencies. In the same alert, CISA encourages every organization to prioritize catalog flaws. It is not a legal deadline in Brazil or the rest of the region.
Does this describe a CGT client?
No. There is no CGT case, client, or result in this article.
Related reading
The piece on the October Windows Server update and on-premises Exchange describes the problem Computerworld says the November package closed. Another piece, on fake IT support in Microsoft Teams, covers a different kind of rush: someone shows up under a trusted name and asks for control of the PC.
How CGT can help
CGT supports small and mid-sized businesses with IT management and Microsoft 365, within the scope agreed with each client: see which PCs still have desktop Outlook on a build older than the November 10 note, apply the Office update, and write down what the team does with a file it was not expecting. Human support is Monday to Friday, 08:00 to 18:00, São Paulo time.
Want to check the Outlook build on the company’s PCs? Meet CGT and talk to us.
Sources: Microsoft, CVE-2026-124194, Nov. 10, 2026, Office security release notes, Nov. 10, 2026, CISA alert, Nov. 10, 2026, CISA KEV catalog, SecurityWeek, Nov. 10, 2026, Malwarebytes, Nov. 11, 2026, and Computerworld, Nov. 13, 2026.


