Tech basics

Security alert

November's Patch Tuesday: update Outlook now, attackers are exploiting a flaw that leaks your Windows sign-in

Microsoft says an Outlook flaw fixed November 10, 2026 is already being exploited. Here is what it does, which Office builds fix it, and the other November patches small offices should prioritize.

Microsoft’s November 10, 2026 security updates fix CVE-2026-124194, a flaw in desktop Outlook for Windows that Microsoft marks as exploited. The Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities (KEV) catalog the same day. If your office uses Outlook from Microsoft 365, Office LTSC 2021, or Office LTSC 2024, make sure every PC has this month’s Office update this week.

It is the only November fix Microsoft lists as exploited. A few others, covered further down, deserve quick attention if you run your own domain controllers or Exchange server.

What the Outlook flaw does, in plain words

Microsoft describes it this way: an attacker sends a specially crafted file and talks someone into opening it in Outlook. Opening it can make Outlook reach out to a computer the attacker controls, without showing the warning Outlook normally shows before contacting outside content.

That quiet connection can hand the attacker a scrambled copy of the person’s Windows sign-in (Microsoft says an NTLMv2 hash, a form of the password Windows uses to prove who you are). Microsoft says the attacker could use it to sign in as that person.

A few things that limit it:

  • Someone has to open the file. Microsoft says the Preview Pane is not a way in, so just seeing the message in the inbox list or preview isn’t enough.
  • It’s rated Moderate, with a CVSS score of 6.5. The low score reflects that a person has to be tricked first. It doesn’t make it safe to wait, because Microsoft says it’s being used now.
  • Microsoft lists no workaround. The update is the fix.

The details

  • CVE: CVE-2026-124194, “Microsoft Outlook Spoofing Vulnerability” (CWE-356, the program doesn’t warn the user about an unsafe action)
  • Exploitation: Microsoft says “Exploited: Yes” and “Publicly Disclosed: No”; CISA lists ransomware use as “Unknown”
  • CISA due date: November 24, 2026 for federal agencies. Government offices and banks that follow KEV dates should plan to be done by then.
  • Products Microsoft lists: Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024, all on Windows. Microsoft’s list doesn’t include Outlook on the web, Outlook for Mac, or the phone apps.

Which Office build fixes it

Microsoft’s release notes for November 10, 2026 list these builds, and CVE-2026-124194 is in that release’s Outlook fixes:

Office version Fixed version and build (or later)
Microsoft 365, Current Channel Version 2610, build 20527.20196
Microsoft 365, Monthly Enterprise Channel 2610 (20527.20194), 2609 (20430.20264), or 2608 (20326.20320)
Microsoft 365, Semi-Annual Enterprise Channel 2610 (20527.20192), 2609 (20430.20262), or 2608 (20326.20318)
Office 2024 and 2021 retail (bought once, not volume licensed) Version 2610, build 20527.20196
Office LTSC 2024 (volume licensed) Version 2408, build 17932.21140
Office LTSC 2021 (volume licensed) Version 2108, build 14334.21048

How to check and update one PC

Most Microsoft 365 installs update themselves within a few days, but “most” isn’t “all.” To check a PC by hand:

  1. Open Outlook (classic Outlook, the one with the File menu).
  2. Go to File > Office Account. In Word or Excel it’s File > Account.
  3. Under Product Information, select Update Options > Update Now. If you only see Enable Updates, select that first.
  4. When it finishes, restart Outlook, go back to the same page, and compare the version and build shown there with the table above.

If Update Options is missing and you only see an About button, the PC’s updates are controlled centrally, usually by your IT company or a volume license setup. Ask whoever manages that to confirm the November build is deployed.

Still on Office 2016 or 2019? They aren’t on Microsoft’s list for this flaw because they’re past end of support: Microsoft ended support for Office 2016, Office 2019, Outlook 2016, and Outlook 2019 on October 14, 2025. Unsupported versions don’t get security fixes, so plan the move to a supported version.

For whoever runs the network

Two extra steps help against this kind of sign-in leak in general. They don’t replace the patch.

  • Block outbound SMB to the internet. Microsoft’s guidance is to block TCP port 445 outbound to the internet at your firewall, since offices rarely need it. Its main exceptions are Azure Files and Office 365 scenarios, so check before you block. If you inherited the firewall, our firewall rule review covers what else to look for.
  • Put admin accounts in Protected Users. Microsoft says members of the Protected Users group can’t use NTLM to sign in to the domain, so a leaked NTLM hash is worth less for those accounts. Microsoft warns not to add service or computer accounts, and to test before adding Domain Admins. See Separate admin accounts and Protected Users.

The other November fixes worth prioritizing

None of these are marked exploited. Microsoft rates each Critical and says exploitation is “More Likely”, so they come right after the Outlook update for shops that run these servers:

  • Domain controllers: CVE-2026-118146, remote code execution in Active Directory Domain Services (CVSS 8.8), and CVE-2026-118148, elevation of privilege (CVSS 7.5). Both need an attacker who already has a low-level domain account, which is exactly what a phished user’s account gives them. Fixes include KB5131291 (Server 2016), KB5131085 (Server 2019), KB5131090 (Server 2022), and KB5131080 (Server 2025; hotpatch-enrolled Azure Edition servers get KB5131077).
  • Exchange Server: CVE-2026-118207, remote code execution (CVSS 8.8), also needing a low-level account. Microsoft lists Exchange Server Subscription Edition, fixed by KB5133453 (build 15.02.2562.057). Exchange 2016 and 2019 reached end of support October 14, 2025.
  • Windows Schannel (CVE-2026-119952) and Windows NAT (CVE-2026-113862), both remote code execution with no sign-in needed, though Microsoft rates attack complexity as high. Both are covered by the regular November Windows cumulative update.

For PCs, the regular November Windows update covers all of the Windows items. Our guide to keeping office computers updated covers how to roll updates out without breaking things.

Sources

All articles