Microsoft shipped November's updates on November 10, roughly 1,094 fixes with about 63 rated critical, making it the second-largest Patch Tuesday on record after October's. One flaw is confirmed to be exploited: CVE-2026-124194, an Outlook spoofing vulnerability that can leak a user's NTLMv2 hash when they open a crafted message file.
Why a leaked hash matters
An NTLMv2 hash is not the password, which is why this gets filed as spoofing rather than something scarier. It is a cryptographic value derived from the password during authentication, and it is useful to an attacker in two ways.
They can try to crack it offline, which is fast and cheap against a short or common password and slow against a long one. Or, in some configurations, they can relay it, using the hash to authenticate as that person somewhere else without ever learning the password at all.
The practical shape is what makes it worth a paragraph: there is no macro to enable, no attachment to run, no credential page to be fooled by. A user opens a message. That is the whole interaction. Every piece of advice we give people about pausing before they click is bypassed, because the clicking already happened in the ordinary course of reading email.
On the number, briefly
Counts differ again. Tenable says 1,093, most outlets say 1,094 or 1,095, and CrowdStrike reports 1,252 on a broader scope. Critical counts range from 63 to 68. The vendors are measuring slightly different things rather than being careless, and we noted the same spread in October.
The conclusion is the one we keep landing on: the headline figure is not a decision input. Nobody triages a thousand items. The monthly question is narrower, is anything being exploited right now and does it affect what we run, and this month the answer is yes and almost certainly yes.
The connection to last weekend
Two days ago we covered an intrusion in which a jailbroken AI agent spent fourteen days inside a telecom using a flaw that had been patched since August. The link to today is direct. The thing an endlessly patient attacker grinds against is a backlog of known, published, already-fixed vulnerabilities. A thousand-CVE release is only frightening if the updates do not actually install.
What to actually do
- Make sure November's updates land this week, on every machine. Including the laptop of whoever is travelling and the back-office PC nobody logs into.
- Verify they applied, rather than that they are enabled. A device that has deferred updates for three months looks perfectly healthy from the outside.
- Treat long passwords as the mitigation they are. A leaked hash for a 20-character passphrase is a much worse purchase than one for an eight-character password, which is the practical argument for passphrases and passkeys.
- Ask your IT provider whether NTLM is still needed anywhere in your environment. Many small businesses no longer need it and have never turned it off.
- Do not build staff advice around not clicking. This flaw triggers on opening a message. The habits worth reinforcing are verification of requests, not suspicion of the inbox itself.
- Check Windows versions are still supported while you are in there. Patches only help the versions still receiving them.
The takeaway
Our fifth Patch Tuesday post, and the count has stopped being the story. What is worth five minutes each month is the single question of whether anything in the pile is already being used against people. This month it is a flaw that leaks a credential hash from the act of opening an email, which is a good reminder that user caution is a layer and not a control.