Skip to main content

Patch Tuesday November 2026: an Outlook flaw already exploited, and more than 1,000 fixes

The November 2026 Patch Tuesday fixes over 1,000 flaws, including an exploited Outlook bug fixed via Office, not Windows. What to install and how to check.

Updated 14 November 2026 · 4 min read

On Tuesday 10 November 2026, Microsoft released its monthly security fixes. The volume is still extraordinary: more than 1,000 vulnerabilities fixed, the second biggest month on record after October. Only one flaw is already exploited, but it comes with a catch: it is fixed by the Office update, not the Windows update.

The short answer

In November 2026, first install the Office (Outlook) update to fix CVE-2026-124194, which is already exploited, then the Windows 11 cumulative update KB5132061. An up-to-date device shows build 26300.9974 (26H2) or 26200.9974 (25H2). To see at a glance which devices in your fleet are still behind, LongLife continuously shows the update status of every device.

This month's figures

IndicatorNovember 2026
Release dateTuesday 10 November 2026
Microsoft vulnerabilities fixedabout 1,094 (counts vary by source)
Critical63
Important1,029
Already exploited (zero-day)1, in Outlook
Made public before the fix0

Totals differ from one security vendor to another depending on whether they count the Chromium fixes (for Edge) republished by Microsoft. The order of magnitude is not in doubt.

The flaw to fix first: CVE-2026-124194 (Outlook)

  • Type: spoofing in Outlook, CVSS score 6.5.
  • Risk: the attack can leak the user's NTLMv2 hash, a fingerprint of their Windows password that can be reused to try to reach other resources on the network.
  • Status: already exploited, listed in the US CISA Known Exploited Vulnerabilities catalog.
  • Fix: the Office or Outlook update. The Windows update is not enough.

Do not be misled by its "moderate" score: a flaw that is already exploited comes before a theoretical critical one.

November's Windows updates

Windows 11 versionUpdateBuild after installation
26H2KB513206126300.9974
25H2KB513206126200.9974
24H2 Enterprise and EducationKB513206126100.9974
23H2 Enterprise and EducationKB5131087see Microsoft's release note

Note: Windows 11 24H2 Pro has received no fixes since 13 October 2026. The devices concerned must move to 25H2 or 26H2. Windows 10 devices are only covered if they are enrolled in Extended Security Updates (ESU); we cover this in our article on moving from Windows 10 to Windows 11.

Check a device with one command

Open PowerShell (right-click the Start button, then "Terminal") and run:

PowerShell
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion" | Select-Object DisplayVersion, CurrentBuild, UBR

Read the result like this: CurrentBuild is the build number (26300 for 26H2, 26200 for 25H2), UBR is the revision number. If UBR is 9974 or higher, the November fix is installed.

For the Office version (Microsoft 365 installation, known as "Click-to-Run"):

PowerShell
Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" | Select-Object VersionToReport, CDNBaseUrl

If Office is behind, open any Office app, then File > Account > Update Options > Update Now. On one device, these checks are enough. Across a whole fleet, LongLife runs this check for you continuously, device by device, and lists the devices that have not yet received the fix.

  1. This week: update Office on every device, because of the Outlook flaw that is already exploited.
  2. Day 1 to 2: install KB5132061 on a pilot group (a few IT devices and a volunteer department).
  3. Day 3 to 7: roll out to the whole fleet if no line-of-business application breaks.
  4. In parallel: find the devices still on 24H2 Pro or on Windows 10 without ESU, which no longer receive anything.
  5. Lasting good practice: block outbound SMB traffic (port 445) to the internet at the firewall, which limits the exploitation of NTLM hash leaks.

LongLife: every Patch Tuesday under control, across the fleet

Every month the same question comes back: which devices actually received the fixes? LongLife answers it without you visiting a single device. You see at all times:

  • the Windows update status of each device, so you spot the laggards immediately;
  • the Windows version and its end of support, to isolate the devices that no longer receive anything (24H2 Pro, Windows 10 without ESU);
  • the full security posture: antivirus, firewall, BitLocker;
  • incidents detected across the fleet, with the recommended action and its priority.

For a device that is stuck, you act remotely with a signed script, or you raise an on-site work order. Devices too old to keep up are flagged with a costed recommendation: upgrade or replace, with the cost and CO₂e of each option.

The free plan covers up to 15 devices. Book a meeting to see your fleet in LongLife, estimate the savings with the simulator, or read our guide to IT asset management.

Next Patch Tuesday: Tuesday 8 December 2026.

Sources

Frequently asked questions

What is Patch Tuesday?

It is the day Microsoft releases its monthly security fixes, the second Tuesday of each month, around 7 pm Paris time (10 am US Pacific time). The next one falls on Tuesday 8 December 2026.

What is the November 2026 Windows 11 update?

KB5132061 for Windows 11 26H2 and 25H2, and for 24H2 on Enterprise and Education editions. Up-to-date devices show build 26300.9974 (26H2), 26200.9974 (25H2) or 26100.9974 (24H2).

Which flaw should be fixed first in November 2026?

CVE-2026-124194, a spoofing flaw in Outlook already exploited by attackers. It can leak a fingerprint of the user's Windows password (NTLMv2 hash). It is fixed by updating Office, not Windows.

Should fixes be installed as soon as they are released?

For a flaw that is already exploited, yes, within days. For the rest, good practice is to install first on a small group of pilot devices, then across the whole fleet within the week, once you have checked that line-of-business applications still work.

How much longer can your fleet last?

The simulator estimates in one minute the budget and CO₂ saved by extending your renewal cycle.

Read next