← Back to blog
#Ciberseguridad#Microsoft#Outlook#Actualizaciones#Pymes

Microsoft's November Patch: An Already-Exploited Outlook Zero-Day and What to Update This Week

Laptop with the words “Cyber Security” in red on the screen

On Tuesday, November 10, 2026, Microsoft released its monthly batch of security updates (the well-known "Patch Tuesday"). According to BleepingComputer's roundup and CSO Online's analysis, this month brings an unusually large number of fixes and an Outlook zero-day that is already being exploited. If your company uses Microsoft 365 or Office, this one is for you.

The zero-day: Outlook and credential theft

The flaw is tracked as CVE-2026-124194, a spoofing vulnerability in Microsoft Outlook. Both sources describe the mechanism the same way: an attacker sends a crafted message file and persuades the person to open it. When that happens, Outlook connects to a network location controlled by the attacker without showing the usual external-content warning. That connection can leak the user's NTLM authentication hash, which the attacker can try to crack to recover the password or reuse to impersonate the victim.

  • It needs user action: the file must be opened. It is not a "zero-click" attack.
  • Affected products: Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024.
  • Status: Microsoft lists it as actively exploited. Its base severity is moderate, but that doesn't change the urgency: a stolen hash is a very common stepping stone before a bigger incident.

A record-sized month (with counts that depend on who is counting)

This month's patch counts were published with different totals. BleepingComputer reports 1,235 vulnerabilities and includes 142 from Microsoft Edge (Chromium-based) in its breakdown; CSO Online counts 1,094 from Microsoft, 63 of them critical. Even BleepingComputer's own breakdown doesn't add up exactly to its total (the categories reach 1,226), so don't treat any single figure as definitive. What matters is not the exact number but the takeaway: there are more than a thousand fixes, and several affect servers.

Among the critical ones highlighted by BleepingComputer and CSO Online (each covers some):

  • CVE-2026-118207: remote code execution in Exchange Server. CSO places it among the 9.8-rated flaws and notes it can be triggered by anyone able to send email to the organization.
  • CVE-2026-119958: remote code execution in the Windows LDAP service, which, per CSO, lets an unauthenticated attacker run code and puts domain controllers and Active Directory at risk.
  • CVE-2026-118146 and CVE-2026-118148: remote code execution and privilege escalation in Active Directory Domain Services.
  • CVE-2026-122194: remote code execution in Microsoft Defender.

The same update cycle included fixes from other vendors: Google patched an exploited zero-day in Chrome, and SAP, Cisco and others issued critical advisories. If you manage user devices, browsers also need updating this week.

What this means for your SME

Most Ecuadorian SMEs rely on Microsoft email and office software, and many have a Windows server or an on-premises Exchange that nobody updates until something breaks. The risk is not abstract: a password stolen this way can open email, the VPN or the accounting system. Above all, the patch on user devices doesn't always install itself: it depends on how Microsoft 365 Apps updates are managed.

What to do this week

  1. Update Microsoft 365 Apps / Office on every device (File → Office Account → Update Options → Update Now) and confirm the installed version. In managed environments, push the update from your console.
  2. Prioritize servers: on-premises Exchange (if you have it), domain controllers and anything exposed to the internet. Schedule a maintenance window and take a backup first.
  3. Update browsers (Chrome and Edge) and restart them.
  4. Limit the impact of a stolen hash (our recommendation, not part of the bulletin): block outbound SMB (port 445) to the internet at the firewall and, where your software allows it, restrict NTLM. Turn on two-step verification for email.
  5. Warn your team: don't open message files (.msg) or unexpected attachments, even if they seem to come from a known supplier. A well-configured mail filter helps, but training remains part of the defense.
  6. Verify, don't assume: ask whoever manages your devices for a report of which machines are still unpatched.

To review the pattern of other recent flaws, see our posts on the critical Jira and Confluence flaw and on the end of Windows 10 support: in both cases the real problem was not knowing which devices were out of date.

How we approach it at SimCodec

At SimCodec we help companies keep an inventory of devices and servers, plan update windows with a prior backup, and strengthen email and access with two-step verification. If you don't know for sure how many of your devices have this patch, that is a good place to start. Contact us and we'll review it with you.

Sources

← Back to blog Get a quote →