Microsoft's November Patch Tuesday arrived on 10 November with 1,094 vulnerabilities fixed across its products, 63 of them rated Critical, by Qualys's count. Add the Chromium fixes that ship through Edge and the total passes 1,200. Nobody is going to read 1,094 advisories. The useful question is which handful of them change what you do this week.
Here is how we would answer it.
One bug is already being used
Out of that whole list, Microsoft marks exactly one as "Exploitation Detected": CVE-2026-124194, a spoofing flaw in Outlook.
On paper it looks skippable. Microsoft rates it Moderate and gives it a CVSS score of 6.5. In practice it is the most urgent item in the release, because someone is using it right now.
The mechanics, as Microsoft describes them, are simple. An attacker sends a specially crafted message file. If the recipient opens it, Outlook connects to a network location the attacker controls without showing the usual warning about external content. That connection can hand over the user's NTLMv2 hash, which Microsoft says could then be used to authenticate as that user.
Two details decide how worried you should be:
- The user has to open the file. Microsoft states that the Preview Pane is not an attack vector, so receiving the message is not enough on its own.
- No credentials are needed to send it. The attacker does not have to be inside your network or logged in to anything first.
The affected products are the desktop Outlook builds in Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024. CISA added the flaw to its Known Exploited Vulnerabilities catalog on the day of release and gave US federal agencies until 24 November to fix it. That deadline binds nobody else, but it is a fair signal of how the people who watch attacks for a living rank it.
Microsoft has not published a workaround. The fix is the November Office update.
Three that are quiet for now, but could hurt more
The highest scores this month belong to bugs nobody has been seen using. They still deserve an early slot because of where they sit.
| CVE | Component | CVSS | Why it is serious |
|---|---|---|---|
| CVE-2026-116928 | Windows Search | 9.8 | Remote code execution over the network, with no login and no user action |
| CVE-2026-119958 | Windows LDAP | 9.8 | Same profile, and the code would run inside the LDAP service |
| CVE-2026-119952 | Windows Schannel | 8.1 | Harder to pull off, but Microsoft rates exploitation "more likely" |
If you run Active Directory, think about the LDAP flaw first, because LDAP is what domain controllers do all day. The Schannel bug depends on specific protocol settings and carries a high-complexity rating, yet it is the only one of the three that Microsoft rates as more likely to be exploited. All three affect Windows 10, Windows 11 and Windows Server 2016 through 2025.
Exchange administrators have one more to note: CVE-2026-118207, a remote code execution flaw in Exchange Server that needs an authenticated attacker.
The order we would patch in
- Desktop Outlook, everywhere. Push the November update for Microsoft 365 Apps and Office LTSC to every machine that runs Outlook. It is exploited, it is on the KEV list, and it is one update.
- Domain controllers and Exchange servers. These carry the LDAP, Search, Schannel and Exchange fixes, and they are the machines an attacker most wants.
- The rest of the Windows fleet. Qualys counts 726 of this month's fixes in Windows alone. The cumulative update covers them together, so this is a rollout problem, not a reading problem.
- Block outbound SMB at the edge. This is our advice, not Microsoft's. If workstations cannot open connections to the internet on TCP port 445, a whole family of hash-leaking tricks stops working, including ones nobody has found yet. Restrict NTLM where you can.
- Write down what you installed. Keep the build numbers. When someone asks next month whether you were exposed, you will want the answer in a file, not in someone's memory.
If you also run Adobe software, the same day brought nine Adobe advisories covering 63 vulnerabilities, four of them critical, in products including Photoshop, Premiere and After Effects.
What we take from this
Severity labels make a poor to-do list. This month the bug being exploited is a "Moderate" 6.5, and the 9.8s are quiet. Sort by score and work down, and you reach the one that matters last. Sort first by what is being used, then by what sits on your most valuable machines.
The other lesson is volume. A release this size cannot be triaged by hand, whoever you are. What a small team can do is decide in advance which machines get updates first, let Office update itself, and close the outbound ports that turn one opened file into a stolen login. That is an afternoon of work, and it pays off every month from now on.