Windows Update Won't Fix This One

Microsoft repaired a flaw in Outlook this week that attackers are already using. The awkward part is not the flaw, it is where the repair lives: it arrives with Office rather than with Windows. So a computer whose Windows Update screen is clean and green can still be running the version with the hole in it, and the person looking at that screen has no way to tell.

Microsoft released its monthly batch of repairs on November 10. One of them matters more than the rest, because attackers are already using it and because of where the fix arrives. It is a flaw in Outlook. The repair does not come through Windows Update. It comes with Office. That distinction sounds like bookkeeping and is not. Most people have one mental model of updating a computer, and it is the Windows Update screen. Office updates itself separately, on its own schedule. Neither one tells you about the other. Our interest, and it is not a flattering one. Patching is work we are paid to do. If we manage your machines, this is ours to have handled rather than yours to chase — so the right response to this article, if you are a client, is to ask us and make us show you a version number. The technical part — you can skip this box Microsoft's own page is the "Release notes for Microsoft Office security updates" on its documentation site, with a page date of November 10, 2026. We read it. Under the heading "November 10, 2026" it lists affected products, and under the sub-heading "Outlook" it lists exactly one catalogue number — a catalogue number being the industry's case number for one specific flaw — CVE-2026-124194 . The same page lists the builds Microsoft dates to November 10, in its own words: Current Channel "Version 2610 (Build 20527.20196)"; Monthly Enterprise Channel "Version 2610 (Build 20527.20194)"; Semi-Annual Enterprise Channel "Version 2610 (Build 20527.20192)"; Office LTSC 2024 Volume Licensed "Version 2408 (Build 17932.21140)"; Office LTSC 2021 Volume Licensed "Version 2108 (Build 14334.21048)"; Office 2019 Volume Licensed "Version 1808 (Build 10417.20236)"; and for Mac, "Version 16.115 (Build 26110837)". Read that list as the releases Microsoft dates to November 10 and nothing more. The page does not say these are the first builds to contain the fix, and it does not say which earlier builds are affected. We are not going to turn a list of current releases into a threshold Microsoft did not state — a version number published in the wrong direction is worse for you than no version number at all. What we could not read: Microsoft's own advisory page for this flaw renders entirely in the browser and returns an empty shell to us, so everything below about exploitation and about how an attack arrives comes from two named secondary sources rather than from Microsoft directly. Those sources are SOCRadar, published November 11, and CyberInsider, published November 10 by Bill Mann. Both say Microsoft reports the flaw as exploited. SOCRadar describes it as "an Outlook spoofing vulnerability rated Moderate with a CVSS v3.1 score of 6.5" and says "Microsoft lists CVE-2026-124194 as exploited"; CyberInsider says "Microsoft reports active exploitation but says the issue was not publicly disclosed before the patch." On how it works, SOCRadar says "An unauthenticated attacker can send the file, but the target must open it; Microsoft states that the Preview Pane is not an attack vector," and CyberInsider says "Exploitation requires the user to open the malicious file; Microsoft explicitly rules out the Preview Pane as an attack vector." Both agree on the two points that matter to a reader: somebody has to open something, and merely having the message selected in the reading pane is not enough. On where the fix lives, SOCRadar says it "ships through Office security updates, including those for Microsoft 365 Apps for Enterprise and Office LTSC 2024, not in the Windows cumulative update KB5132061," and CyberInsider says "installing the Windows cumulative update alone does not address the Outlook vulnerability." One number we are not giving you: the total count of flaws fixed this month is reported as 1,094 by two outlets and 1,235 by a third, we found no Microsoft page carrying either, and the figure does not change what you should do. What that actually means Your computer has two separate updaters and most people have seen one. Windows keeps itself current. Office keeps itself current. They do not report on each other. So a green Windows Update screen is not an answer to this question. It answers a different question that looks the same. Somebody still has to open a file for this to work. That is a real limit, worth knowing rather than glossing over. Having the message highlighted in the list is not enough. The part that is actually good news The repair exists, it is free, and the check takes about as long as making coffee. Nothing to buy, nothing to schedule, nobody to call. For most offices it will turn out to be already done, because Office updates itself by default on a healthy machine. Finding out takes a minute and leaves you certain. The caveat, which is a check rather than a fear Office updates itself only where nothing has stopped it. On machines set up by somebody's nephew in 2019, on machines joined to an old network policy, and on the laptop that lives in a drawer, automatic updating is often quietly switched off. So the check is the version, not the policy. A setting that says updates are on is a claim. A date on the version screen is evidence. What to do in ten minutes Open Word or Outlook on one machine. Click File, then Account, then Update Options, then Update Now. If it installs something, that machine was behind. Do the same on the laptop nobody uses. That is the one this finds. If the update button is greyed out or missing, that is the finding. Something is managing it, and somebody should know what. Do not go hunting for build numbers. Microsoft has not published which build is the first safe one in a form we can read, so the update button is a better test. If we manage your machines, ask when Office last updated and expect a date rather than a reassurance.