Cybersecurity · November 18, 2026 · ComputerKing Team

Opening One Outlook Attachment Leaked the Login Credential: CVE-2026-124194 Was Already Being Exploited — and Windows Update Will Not Fix It

Microsoft's 10 November Patch Tuesday fixed about 1,090 vulnerabilities, and only one was confirmed as already exploited: Outlook zero-day CVE-2026-124194. Opening a specially crafted message file makes Outlook quietly connect to an attacker-controlled server, leaking the user's NTLMv2 login hash. The easiest trap is that the fix ships through Office updates, not Windows Update — Windows Update alone will not patch it. This guide shows how to check your build, update Office, and what to do if you already opened a suspicious file. Pricing is quoted case by case.

Opening One Outlook Attachment Leaked the Login Credential: CVE-2026-124194 Was Already Being Exploited — and Windows Update Will Not Fix It

Key summary

On 10 November 2026, Microsoft shipped its November Patch Tuesday, fixing about 1,090 vulnerabilities in one release. Only one of them carried Microsoft's "exploitation detected" flag: zero-day CVE-2026-124194 in classic Outlook. Opening a specially crafted message file makes Outlook connect to an attacker-controlled server without showing its usual external-content warning, leaking the user's NTLMv2 login hash along the way — an attacker can use it to sign in as you. The US CISA added it to its Known Exploited Vulnerabilities catalogue the same day. The easiest trap is this: the fix ships through Office updates, not Windows Update, so Windows Update alone will not patch it.

1. How the flaw works: it goes wrong the moment you open the file

  • Reference: CVE-2026-124194, classified by Microsoft as an Outlook spoofing vulnerability, severity Moderate, CVSS 6.5.
  • Trigger: an attacker sends a specially crafted message file and persuades the user to open it in an affected version of classic Outlook. Merely glancing at it in the preview pane does not trigger it — the file has to actually be opened.
  • What happens: after opening the file, Outlook connects to a server the attacker controls, without showing the external-content warning that would normally appear; during the connection, Windows hands over the user's NTLMv2 authentication response.
  • Consequences: with the NTLMv2 hash, an attacker can try to replay, relay or crack it to sign in as the user. Microsoft rates the severity Moderate because the user has to actively open the file; even so, CISA listed it as a known exploited vulnerability because exploitation has been confirmed.
  • Scope: Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024, in both 32-bit and 64-bit editions.

2. Why so many people will miss this patch: Windows Update does not cover Office

This is the most important point in this article. Many users assume "Windows Update says I am up to date" means they are safe, but the fix for CVE-2026-124194 is not in the November Windows cumulative update KB5132061 — it ships through Office updates.

The fixed builds are:

  • Office LTSC 2021: 16.0.14334.21048
  • Office LTSC 2024: 16.0.17932.21140
  • Microsoft 365 Apps: Current Channel 2610 build 20527.20196 (the build released on 10 November 2026)

If you only run Windows Update, Outlook stays on the unpatched build. Company environments need extra care: Office updates may be rolled out centrally by IT, so they do not necessarily reach every machine automatically.

3. Do this now: 30 seconds to check the build and update Office

1. Check the build in Outlook: File → Office Account → About Outlook, and look at the build number. Compare it with the three fixed builds above: a build number equal to or higher than the listed one means it is patched.

2. Update Office: File → Office Account → Update Options → Update Now. Wait for it to finish, then open About Outlook again and confirm the build number has changed.

3. If a work PC does not let you update yourself: ask IT whether this Office update is scheduled for rollout. Do not go looking for installer files from unknown sources.

4. Do not assume the update erases the past: if you previously opened a message file of unknown origin, updating only closes the hole — any credential already leaked does not become invalid because of the update. Follow the steps in the next section too.

4. If you may have opened a suspicious file, do this

If you opened a .msg file you were not sure about, or Outlook showed a strange external-content prompt:

1. Change the password at once: change your Microsoft account or work account password, and do not just add a digit to the old one.

2. Turn on multi-factor authentication: if it is not on yet, now is the time; after an NTLM hash leak, multi-factor authentication is the key defence against sign-in impersonation.

3. Check the sign-in history: on the Microsoft account sign-in activity page, look for sign-ins from places or devices you do not recognise.

4. Tell company IT: for a work account, say so at once so IT can check whether other accounts are affected. Do not wait until someone uses your account to send spam.

5. Do not open similar files again: if a .msg attachment arrives from an unfamiliar sender or with content that does not add up, do not open it; if in doubt, ask the sender whether they really sent it.

5. How ComputerKing can help

  • 🔍 Office build check: we check the build, run the Office update, and confirm CVE-2026-124194 is patched
  • 🔒 Account security check: password reset, multi-factor authentication setup and sign-in history review, done in one visit
  • 💾 Backup check: if an account really has been abused, an offline backup is the last line of defence

📞 WhatsApp 2115 9219 to book, or visit us at Room 1209, Dalton Plaza, 18 On Lai Street, Shek Mun, Shatin.

*Last updated: 18 November 2026. This article is based on public information from the Microsoft Security Response Center, the CISA Known Exploited Vulnerabilities catalogue, SecurityWeek and others; Microsoft has not published the attacker's identity or victim details. Pricing is quoted case by case.*

Frequently Asked Questions

I only read emails in Outlook and never open attachments. Can I ignore this?

No. The trigger is opening a specially crafted message file, not ordinary reading. But as long as Office stays unpatched, the risk stays — you never know when such a file will arrive. Checking the build and updating Office is the direct fix.

Windows Update says I am up to date. Does that mean I am patched?

No. The fix for this flaw ships through Office updates, not in the Windows cumulative update. You have to check the build number inside Outlook against the fixed builds to be sure.

I use Outlook on the web. Am I affected?

This flaw affects classic Outlook for Windows only; Outlook on the web is not on the affected list. But if the same machine also has desktop Outlook installed, check its build anyway.

I changed my password. Am I safe now?

Changing the password is a necessary first step, but not the whole job. If Office is still unpatched, the hole is still there; without multi-factor authentication, the next credential leak can be abused the same way. Update, change the password, and turn on multi-factor authentication — all three together.

WhatsApp 2115 9219