Outlook Zero-Day Is Being Exploited: Update Outlook Today
Watch the Short on YouTube: https://www.youtube.com/shorts/W17aeVbhWR0 Also on LinkedIn: https://www.linkedin.com/feed/update/urn:li:activity:7528150342761517056/
If your clients run the Outlook desktop app, this is the one to move to the top of the list this week. On Patch Tuesday, November 10, 2026, Microsoft fixed an Outlook flaw, CVE-2026-124194, and marked it as exploited. CISA put it in the Known Exploited Vulnerabilities catalog the same day.
I made a short video for end users. This post is the longer version for those of us who have to roll the fix out across a lot of desks and explain to leadership why it matters.
What Microsoft says
Microsoft calls CVE-2026-124194 an Outlook spoofing vulnerability. In the Security Update Guide it is marked "Exploitation Detected." It was not publicly disclosed before the patch shipped.
From Microsoft's FAQ on the entry, here is the chain:
Someone sends a specially crafted message file.
The user opens it.
Outlook connects to a location the attacker controls, and it does so without showing the usual external-content warning.
That connection discloses the user's NTLMv2 hash.
An attacker could use that hash to authenticate as the user.

One piece of good news, straight from Microsoft: the Preview Pane is not an attack vector. Just previewing the email does not trigger it. The file has to be opened.
Where it stands today
The story broke on November 11, so I re-checked everything on November 16 before writing this.
Patch: available. Microsoft's entry still shows a single revision, the original November 10 publication.
Exploitation: still marked "Exploitation Detected" by Microsoft.
CISA KEV: listed, added November 10, 2026, with a due date of November 24, 2026 for federal civilian agencies.
NVD: the record shows as analyzed.

That KEV deadline is a federal mandate, not a rule for private businesses. I still treat it as a useful outside yardstick. When CISA gives agencies 14 days, a small business with no patch plan is not in a better position than an agency.
Who is affected, and which builds fix it
Microsoft lists three affected products:
| Product | Fixed build | |---|---| | Office LTSC 2021 | 16.0.14334.21048 or newer | | Office LTSC 2024 | 16.0.17932.21140 or newer | | Microsoft 365 Apps for Enterprise | Install the latest security update for your update channel |
For Microsoft 365 Apps, Microsoft points to its Office security release notes rather than one build number, because the fixed build depends on the update channel. Check the channel your tenant actually uses before you mark a machine as done.
The four fixes from the Short

1. Update Outlook now. In Outlook, go to File, then Office Account (in other Office apps it is just Account), then Update Options, then Update Now. That is Microsoft's own path for installing Office updates.
2. Check the version number. Compare it to the table above. On Microsoft 365 Apps, confirm you are on the latest security update for your channel.
3. Do not open message files you were not expecting. That goes for files from names you know, too. The attack needs the user to open the file, so this habit closes the door even on a machine that has not updated yet.
4. IT teams: block outbound SMB on TCP port 445 to the internet. Microsoft's SMB hardening guidance says to block TCP 445 outbound at the corporate firewall, and CISA's SMB best practices say the same for boundary devices. To be clear, Microsoft's entry for this CVE does not say the attack uses SMB. I include it because it is standard hardening. Microsoft notes that blocking it stops devices inside your network from sending data over SMB to the internet, and few businesses have a reason to allow that. Worth having in place before the next bug like this.
Patch first. Then breathe.
Why this one matters to MSPs
A few things I would bring up with your team and your clients.
Do not let the severity label decide the queue. Microsoft rates this one Moderate, with a CVSS score of 6.5. If your patch policy sorts by severity, a Moderate can sit behind a stack of Criticals. But "Exploitation Detected" and a KEV listing tell you more about real risk than the base score does. My advice: let known exploitation move a patch to the front, whatever its rating.
The Windows update is not the Outlook update. The fix ships through Office updates, not the Windows cumulative update. If your reporting only shows Windows patch status, you could see a green dashboard while Outlook is still unpatched. Make sure your tooling reports Office build numbers, not just Windows ones.
Give clients a plain-language version. Most people will not remember a CVE number. They will remember "update Outlook today, and do not open files you were not expecting." That is why I made the Short. Feel free to send it to your clients.
Close the loop with leadership. Executives do not need the NTLM details. They need three things: it is being exploited, the fix is out, and here is when every machine will be on a fixed build. Put a date on it.
Watch and share
Watch the Short: https://www.youtube.com/shorts/W17aeVbhWR0 On LinkedIn: https://www.linkedin.com/feed/update/urn:li:activity:7528150342761517056/
If you want a second set of eyes on your Office patch reporting, we are happy to talk shop. hello@chibitek.com
Sources
Microsoft Security Response Center, CVE-2026-124194 Security Update Guide entry: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124194
Microsoft, Office security release notes (Microsoft 365 Apps fix link): https://aka.ms/OfficeSecurityReleases
CVE.org record: https://www.cve.org/CVERecord?id=CVE-2026-124194
NIST National Vulnerability Database: https://nvd.nist.gov/vuln/detail/CVE-2026-124194
CISA Known Exploited Vulnerabilities catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
CISA alert, "CISA Adds Six Known Exploited Vulnerabilities to Catalog" (Nov 10, 2026): https://www.cisa.gov/news-events/alerts/2026/11/10/cisa-adds-six-known-exploited-vulnerabilities-catalog
Microsoft Support, Install Office updates: https://support.microsoft.com/en-us/office/install-office-updates-2ab296f3-7f03-43a2-8e50-46de917611c5
Microsoft Learn, Secure SMB traffic in Windows Server: https://learn.microsoft.com/en-us/windows-server/storage/file-server/smb-secure-traffic
CISA, SMB Security Best Practices: https://www.cisa.gov/news-events/alerts/2017/01/16/smb-security-best-practices
SecurityWeek, "Exploited Outlook Zero-Day Among 1,094 Flaws Patched by Microsoft": https://www.securityweek.com/exploited-outlook-zero-day-among-1094-flaws-patched-by-microsoft/
Malwarebytes, "Microsoft Patch Tuesday fixes Outlook flaw already under attack": https://www.malwarebytes.com/blog/bugs/2026/11/microsoft-patch-tuesday-fixes-outlook-flaw-already-under-attack
CrowdStrike, November 2026 Patch Tuesday: Updates and Analysis: https://www.crowdstrike.com/en-us/blog/patch-tuesday-analysis-november-2026/








Comments