What Happened
On November 10, Microsoft's monthly security updates fixed CVE-2026-124194, a spoofing flaw in Microsoft Outlook. Microsoft's CVE record describes it as Outlook's interface failing to warn the user about an unsafe action. As reported by SecurityWeek, Microsoft says it is aware of active exploitation, and its advisory says the flaw "discloses a user's NTLMv2 hash to the attacker who could use this to authenticate as the user." The victim has to open a crafted message file. Viewing it in the Preview Pane is not enough.
The same day, CISA added the flaw to its Known Exploited Vulnerabilities (KEV) catalog. Federal agencies have until November 24 to fix it.
Affected products are Microsoft 365 Apps for Enterprise, Office LTSC 2021 (fixed in build 16.0.14334.21048) and Office LTSC 2024 (fixed in build 16.0.17932.21140).
Why It Matters to Buyers
The score undersells the risk. Microsoft scores this flaw 6.5 out of 10, a medium rating. If your patch process ranks work by severity score alone, this one could sit in the queue while attackers use it. Being on the KEV list is the stronger signal.
A leaked hash is a stolen identity. An attacker who captures a user's NTLMv2 hash can try to sign in as that user. One opened file can become a foothold.
Office updates often lag Windows updates. Many teams watch Windows patching closely but leave Microsoft 365 Apps on slower update channels, or rely on an MSP whose reporting covers only the operating system.
What to Do Now
- Confirm Office builds, not just Windows. Check that Microsoft 365 Apps and any Office LTSC installs have picked up the November updates, including laptops that rarely connect to the office network.
- Ask your MSP for proof. If a partner manages patching, ask for a report showing Office build numbers by device, not just "November patches applied."
- Block outbound SMB to the internet at your firewalls, a common defense against hash-leak attacks like this one.
- Warn users about unexpected message files, especially ones that arrive as attachments from outside the company.
- Watch for odd sign-ins from accounts that may have opened suspicious files.
The Bigger Picture
Severity scores tell you how bad a flaw could be. The KEV list tells you it is being used now. When you evaluate patch management tools or MSP contracts, ask whether they track known-exploited flaws separately, cover Office and third-party apps as well as Windows, and commit to a fix time for KEV items. A partner who can show you Office build numbers this week is one worth keeping.
Not sure your patching covers more than Windows? Stackcurve advisors help IT leaders compare patch management options and hold MSPs to clear patching commitments at no cost to you. Talk to an advisor →
Stackcurve is independent. No vendor pays for placement or editorial influence on this blog. Details are from Microsoft's published CVE record for CVE-2026-124194 (November 10, 2026), CISA's Known Exploited Vulnerabilities catalog addition announced November 10, 2026, and SecurityWeek's November 10, 2026 report on Microsoft's November security updates, which quotes Microsoft's advisory.