The Outlook zero day patched on 10 November: check your firm before 24 November
Microsoft fixed an exploited Outlook flaw on 10 November and CISA set a 24 November deadline. Five checks for regulated San Diego firms this week, and what is still unknown.
Shane Donoher · Published November 18, 2026
The short answer
On 10 November 2026 Microsoft fixed CVE-2026-124194, a flaw in desktop Outlook that attackers were already using. If someone opens a specially crafted message file, Outlook can connect to a server the attacker controls without showing its usual warning, and hand over the user's NTLMv2 hash, which Microsoft says could be used to authenticate as that user. The fix comes with the 10 November Office update. CISA has given US federal agencies until 24 November to deal with it, and that is a sensible deadline for any firm to work to.
For a 10 to 100 person firm, the job this week is short: confirm every PC running Outlook has the November Office update, confirm your firewall blocks outbound SMB to the internet, and ask your IT provider to show you both in writing.
What happened, with dates
- Tuesday 10 November: Microsoft releases the fix. Microsoft's Security Update Guide lists CVE-2026-124194 as an Outlook spoofing vulnerability, rated Moderate with a CVSS 3.1 base score of 6.5, and marks it as exploited. It was not publicly disclosed before the fix. (Microsoft Security Update Guide, 10 November 2026)
- Tuesday 10 November: the only exploited flaw this month. Of the large batch of fixes Microsoft released that day, this was the only one under active attack, and none had been publicly known beforehand. (CyberScoop, 10 November 2026; BleepingComputer, 10 November 2026)
- Tuesday 10 November: CISA adds it to its Known Exploited Vulnerabilities catalog. The catalog entry gives a due date of 24 November 2026. (CISA alert, 10 November 2026; CISA KEV catalog, checked 18 November 2026)
That 24 November date legally binds federal civilian agencies only. CISA's own alert encourages every organisation to prioritise the vulnerabilities in the catalog, so it works well as a benchmark for a clinic, law firm or accounting practice too.
How the attack works, in plain terms
Microsoft's advisory describes the steps:
- An attacker who needs no account at your firm sends a user a specially crafted message file and persuades them to open it in Outlook.
- Opening the file makes Outlook connect to a network location the attacker controls, and the external content warning that would normally appear does not show.
- During that connection the user's NTLMv2 hash is disclosed. Microsoft says the attacker "could use this to authenticate as the user".
Two details matter for staff. First, Microsoft states that the Preview Pane is not an attack vector, so the user has to actually open the file. Second, BleepingComputer notes that a captured hash can potentially be cracked offline to recover the password, which could then be used to get into other accounts. (BleepingComputer, 10 November 2026)
The score of 6.5 looks modest because the attack needs someone to open a file. The exploited status is the reason to act now.
What is still unknown
As of 18 November, Microsoft's advisory does not say who is exploiting the flaw, which organisations were targeted, how many attacks there have been or how the files were delivered. The CISA catalog lists known use in ransomware campaigns as "Unknown". We will update this post if Microsoft or CISA publish more.
Which versions are affected
Microsoft lists three products, in both 32 bit and 64 bit editions (Microsoft Security Update Guide, 10 November 2026):
- Microsoft 365 Apps for Enterprise. Fixed builds depend on your update channel. Microsoft's Office security release notes for 10 November list, for example, Current Channel Version 2610 Build 20527.20196 and Monthly Enterprise Channel Version 2610 Build 20527.20194. (Microsoft Office security release notes, 10 November 2026)
- Office LTSC 2024. Fixed in build 16.0.17932.21140.
- Office LTSC 2021. Fixed in build 16.0.14334.21048.
Outlook on the web, Outlook for Mac and the phone apps are not on Microsoft's list of affected products. If anyone at your firm still uses Office 2019 or Office 2016, note that neither is on the list and Microsoft says support for Office 2019 ended on 14 October 2025. Treat those copies as a replacement job for this quarter.
How to check your firm this week
1. Check one PC yourself
In Outlook, go to File, then Office Account, and look under About Outlook for the version, build and update channel. Compare the build with Microsoft's release notes for your channel. If the build is older than the 10 November build, click Update Options, then Update Now, and restart Outlook once it finishes. Updates usually finish only once Office apps are closed and reopened, so a PC that never shuts Outlook can sit unpatched for days.
2. Find out who owns Office patching
Many small firms assume Windows Update covers Office. Modern Office installs usually update through their own channel, separately from Windows. Ask who is responsible: your IT provider, a staff member, or nobody. Write the answer down.
3. Ask your IT provider five questions
- Have all our PCs running Outlook received the 10 November Office update, and can you send us the report?
- Which update channel are we on, and is there a deadline so staff cannot keep postponing updates?
- Does our firewall block outbound SMB (TCP port 445) to the internet, including on laptops used at home?
- Are any PCs still running Office 2019 or Office 2016?
- Do you get alerts for unusual sign ins, and will you check the last few weeks for anything odd?
4. Block outbound SMB to the internet
Microsoft's guidance on securing SMB traffic recommends blocking TCP port 445 outbound to the internet at your corporate firewall, and says it is unlikely you need to allow it. (Microsoft Learn, Secure SMB traffic in Windows Server, checked 18 November 2026) Attacks of this kind rely on the PC reaching the attacker's server, so this block cuts off a common route even on a PC that has missed an update. Laptops that work from home or on guest Wi Fi need the same rule on the laptop itself, because they are outside the office firewall.
5. Tell staff one simple rule
Do not open message files or attachments you were not expecting, even if they look like a forwarded email, until IT confirms the update is in place. If in doubt, ask the sender on a phone number you already have.
Signs that a hash may already have leaked
Microsoft has not published indicators for this flaw, so look for the general signs that an account is being misused:
- Sign ins from places, devices or times that do not fit the person.
- Password reset or multi factor prompts the user did not start.
- New inbox rules or forwarding to outside addresses.
- Someone recalling that they opened an odd attachment and nothing appeared to happen.
Your IT provider can see sign in logs and network connections that you cannot see from the inbox. If anything looks wrong, ask them to check that account first.
Password and multi factor follow up
If a user opened a suspicious message file on an unpatched PC, act as if their hash may have leaked:
- Change that user's password to a long, unique one. A long password is far harder to crack offline.
- Confirm multi factor authentication is on for their account and that no unfamiliar methods or devices have been added.
- Review their recent sign ins and mailbox rules with your IT provider.
- Apply the same steps first to anyone with admin rights, because their accounts open the most doors.
Firms that handle patient or client data should also follow their own incident procedures and record what was checked. If you have HIPAA or other regulatory duties, talk to your compliance adviser about whether anything needs reporting. This is general information, not legal advice.
Who should own this
For most small firms the answer is the IT provider, with one named person inside the firm who checks the work. That person does not need to be technical. They need to ask the five questions above, get the report back before 24 November, and file it. We covered the wider set of basics in cybersecurity solutions for small business in San Diego, and patching against CISA's exploited list is one of them.
How we help
We look after Microsoft 365 for regulated San Diego firms of 10 to 100 people, including Office update channels, update deadlines so patches actually land, sign in alerts and multi factor settings. If you want someone to confirm your Outlook builds and firewall rules before 24 November, see our Microsoft 365 services or read about our wider cybersecurity services in San Diego. Book a 15 minute call to talk it through.
FAQs
What is CVE-2026-124194?
An exploited flaw in desktop Outlook, fixed by Microsoft on 10 November 2026. Opening a specially crafted message file can make Outlook connect to an attacker's server without warning and disclose the user's NTLMv2 hash.
Does previewing an email trigger it?
No. Microsoft says the Preview Pane is not an attack vector. The user has to open the malicious file.
Which Outlook versions are affected?
Microsoft lists Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024, in 32 bit and 64 bit editions. Outlook on the web, Outlook for Mac and the phone apps are not on the list.
Do private firms have to patch by 24 November?
The 24 November due date in CISA's catalog binds US federal civilian agencies. CISA encourages all organisations to prioritise catalog entries, so it is a sensible target for any firm.
Who is exploiting it?
Microsoft has not said. As of 18 November, the attackers, targets and any ransomware link are not public, and CISA lists ransomware use as unknown.
What should we do if someone opened a suspicious file?
Make sure the Office update is installed, change the user's password to a long unique one, check their multi factor settings, and ask your IT provider to review their recent sign ins and mailbox rules.
---
*This post is general information, not legal or compliance advice. We checked Microsoft's Security Update Guide and Office security release notes, the CISA alert and catalog entry, NVD, BleepingComputer and CyberScoop on 18 November 2026. Details may change as Microsoft and CISA publish more.*