November Patch Tuesday: The Exploited Bug Was the One Rated Moderate
November 2026 Patch Tuesday fixed 1,093 flaws, but the only one attackers were already using was a Moderate Outlook bug whose fix does not come through Windows Update — here is how to prove your fleet actually got it.
The one bug attackers were already using was rated Moderate
Microsoft's November 2026 Patch Tuesday, released November 10, fixed roughly 1,093 vulnerabilities Microsoft itself assigned. Sixty-three were rated Critical. Exactly one was already being exploited in the wild — and Microsoft rated it Moderate.
That bug is CVE-2026-124194, a spoofing flaw in Outlook with a CVSS score of 6.5. A user opens a crafted message file, Outlook connects to an attacker-controlled server without showing its usual external-content warning, and the connection leaks the user's NTLMv2 hash. The attacker can then try to use that hash to sign in as the user. Microsoft confirmed exploitation before the fix shipped, and CISA added the CVE to its Known Exploited Vulnerabilities catalogue the same day, with a remediation deadline of November 24.
There are two lessons here, and both are about how patching actually fails in practice rather than how it fails on paper.
Lesson one: severity-first patching would have buried this bug
Most teams triage Patch Tuesday by severity. Critical first, then High, then everything else when there is time. That is a reasonable rule most months — and this month it would have put the only actively exploited vulnerability near the back of the queue, behind 63 Critical fixes that no attacker is known to be using.
Exploitation status beats severity rating. A Moderate bug with a live exploit is a bigger real-world risk than a Critical bug that exists only in theory. CISA's KEV list exists precisely to encode that distinction, and the deadline it sets — November 24 for this one — is the date that matters, not the CVSS number.
The fix also breaks the usual patching mental model. It does not ship in the Windows cumulative update. Installing KB5132061 on Windows 11 does nothing for this bug. The fix comes through Office's own update channel: Microsoft 365 Apps, or Office LTSC 2024 (build 16.0.17932.21140) and Office LTSC 2021 (build 16.0.14334.21048). Any fleet that measures patch compliance by Windows Update status alone will report itself healthy while Outlook stays vulnerable.
Lesson two: the patch is only half the job — prove it landed
A patch that was never verified is a patch you are guessing about. For this release, verification means three concrete checks on every machine:
- Office build version. Confirm the installed Microsoft 365 Apps or Office LTSC build is at or past the fixed build. Windows build numbers tell you nothing about this one.
- Windows cumulative update. Windows 11 26H2, 25H2, and 24H2 should be on KB5132061 (builds 26300.9974, 26200.9974, and 26100.9974 respectively). That update carries the rest of the month's fixes, including CVE-2026-116928, a 9.8-rated remote code execution flaw in the Windows Search component that Exchange uses for indexing — reachable from an emailed attachment with no click required.
- NTLM posture. The Outlook bug's payload is an NTLMv2 hash. Machines that have already restricted NTLM — outbound NTLM blocked, NTLM auditing enabled, SMB signing enforced — shrink what a leaked hash is worth. This is the same hardening that blunts every NTLM relay and coercion attack, not just this month's CVE.
WinSentinel's audit modules cover exactly these checks on a single machine — Office and Windows build versions, installed update state, and the NTLM and SMB signing settings — free, with no limits, as part of its 64-module audit set. Run it after patching and the report tells you which machines are actually fixed, rather than which ones were merely told to update. For an organization, the same checks roll up centrally through WinSentinel Pro: one view of which machines in the fleet are still on a vulnerable Office build, instead of a hundred separate reports.
Do not forget Chrome
The same week, Google fixed CVE-2026-125350, a use-after-free flaw in Chrome's XML handling with an exploit in the wild. CISA added it to KEV with the same November 24 deadline. Chrome 157.0.8103.50 and later is fixed. Browsers are patched on their own channel too, and Edge shares Chrome's engine — a fleet that only watches Windows Update misses both of this month's exploited bugs.
The takeaway
Patch Tuesday is not a severity-sorted to-do list. It is an exploited-first list, and this month the exploited item was the one a severity sort would have hidden: a Moderate Outlook bug, fixed through a channel most patch dashboards never look at. Patch Office first, verify the build numbers, check the NTLM posture that limits the damage, and do not let a green Windows Update status stand in for proof. The next Patch Tuesday is December 8 — the last one of the year — and the machines still unpatched on November 24 will be the ones carrying this bug into it.