Technical Lead / Web, SaaS & AI
Home / Blog

CVE-2026-124194: The Outlook Zero-Day Stealing Windows Passwords (and How to Patch)

Get new posts by email

Security alerts, SEO and web development guides, sent when they are published.
No spam. Unsubscribe anytime. Privacy Policy
CVE-2026-124194 Outlook zero-day: update Office, not just Windows. Exploited, leaks NTLM hashes, patched November 10, 2026

Updated: November 13, 2026

It's been a rough week for Outlook. Two days before the Microsoft Outlook outage knocked email offline for businesses worldwide, Microsoft patched a more dangerous problem: CVE-2026-124194, an Outlook zero-day that attackers were already using to steal Windows login data.

It was the only actively exploited flaw in Microsoft's huge November 2026 Patch Tuesday release, and CISA has added it to its list of known exploited vulnerabilities. Here's the catch many small businesses miss: the fix comes through Office updates, not Windows Update. If you only patch Windows, Outlook may still be exposed.

This guide explains what the bug does in plain English, who's affected, how to patch it in a few minutes, and the other Outlook and Exchange flaws worth fixing this month.

Quick answer: what is CVE-2026-124194? CVE-2026-124194 is an actively exploited spoofing vulnerability in classic Microsoft Outlook, rated CVSS 6.5. If a user opens a crafted Office file, Outlook can leak their Windows NTLMv2 password hash to an attacker without a proper warning. Microsoft fixed it on November 10, 2026, through Office updates.

What Is CVE-2026-124194?

CVE-2026-124194 is a flaw in how classic Outlook handles certain actions. Normally, Outlook should warn you before doing something risky, like connecting to an unfamiliar outside server. With this bug, it doesn't. Security researchers describe the problem as Outlook failing to alert the user before a potentially dangerous action takes place.

An attacker sends a crafted Office file, usually as an email attachment. When the victim opens it, Outlook can quietly connect to a server the attacker controls and hand over the user's Windows authentication data, known as an NTLMv2 hash.

Microsoft says the flaw was exploited in the wild before the patch was available, which is what makes it a zero-day. Microsoft hasn't said who is using it or who has been targeted. You can read the details in Microsoft's advisory for CVE-2026-124194.

CVE-2026-124194 key facts at a glance

Item Detail
CVE CVE-2026-124194
Type Spoofing (NTLMv2 hash disclosure)
Severity CVSS 6.5, rated Moderate
Exploited Yes, as a zero-day before the patch
How it's triggered The user opens a crafted Office file
Affected Classic Outlook in Microsoft 365 Apps for Enterprise and supported Office editions
Patched November 10, 2026 (Patch Tuesday)
Fix channel Office updates, not Windows Update
CISA KEV Added November 10, 2026; federal deadline November 24, 2026

Why a "Moderate" Bug Is Your Top Priority

A 6.5 score sounds low, especially in a month with dozens of Critical bugs. But severity scores measure how bad a bug could be in theory. Exploitation tells you what attackers are actually doing. This is the only flaw in the release that attackers are known to be using, so it goes first.

Here's why the stolen data matters. An NTLM hash is a scrambled copy of your Windows login. Attackers can use it in two main ways:

  • Crack it offline. With enough computing power, weak or common passwords can be recovered from the hash.
  • Relay it. In some networks, attackers can pass the hash to another service to log in as you, without ever knowing your actual password.

Either way, one opened attachment can become a foothold into email, shared files or other systems. That's the same pattern we saw with AuthMask, where stolen Microsoft tokens opened the door to work accounts.

Who Is Affected?

You're likely affected if your team uses classic Outlook on Windows through:

  • Microsoft 365 Apps, the desktop Office apps included with most Microsoft 365 business plans
  • Supported standalone or LTSC editions of Microsoft Office

Two important details:

  • The user has to open the file. Unlike some Outlook bugs, simply previewing an email in the Preview Pane isn't enough for this one.
  • Check Microsoft's advisory for your exact edition. Microsoft lists which Office versions and update channels get the fix. The new Outlook for Windows and Outlook on the web are updated by Microsoft's servers, so the main risk sits with classic desktop Outlook.

How to Patch CVE-2026-124194 (Office Update, Not Windows Update)

This is the step most people get wrong. Windows Update keeps Windows itself current, but Microsoft 365 desktop apps like Outlook usually update separately through Office's own updater. Here's how to update and confirm it on a Windows PC:

  1. Open Outlook (or Word or Excel; they share the same updater).
  2. Go to File → Office Account (in Outlook it may say Office Account or Account).
  3. Under Product Information, click Update Options → Update Now.
  4. Wait for the download, then close and reopen Outlook when asked. The fix isn't active until Office restarts.
  5. Back on the Office Account page, note the version and build number, and compare it with the fixed build listed for your update channel in Microsoft's advisory.

If you don't see Update Options, your organization manages updates centrally. Ask your IT provider to confirm the November 2026 Office security update has been deployed.

For IT teams: rolling it out

  • Microsoft 365 Apps follow update channels (Current, Monthly Enterprise, Semi-Annual). Check that each channel in use has received the November build, and shorten deferral periods for this release.
  • Intune or Configuration Manager: confirm the Office update ring has pushed the November update and that devices have restarted Office.
  • Volume-licensed Office (LTSC): confirm the November security update is approved and installed.
  • Report on it: list any device still on an older build and follow up before the November 24 CISA deadline. That date is a good target even if you're not a federal agency.

Extra Protection: Stop NTLM Leaks

Patching closes this hole. These steps make the whole class of NTLM-leak bugs much less useful to attackers. They're mainly for IT teams, so if you're a small business without one, pass this section to your IT provider.

  • Block outbound SMB (TCP port 445) to the internet at your firewall. Most NTLM-leak attacks rely on the victim's PC connecting out to an attacker's server on this port. Normal offices rarely need it open to the internet.
  • Use the Protected Users group for admins and high-value accounts. Members of this Active Directory group can't use NTLM, which removes the risk for them.
  • Apply Microsoft's NTLM hardening. The November update also strengthens NTLM authentication. Review Microsoft's guidance and plan to restrict NTLM where your systems allow it.
  • Enforce strong, unique passwords and MFA. A leaked hash of a long, unique password is much harder to crack, and MFA stops many relayed or cracked credentials from being enough on their own.

The Other Outlook and Exchange Flaws to Patch This Month

CVE-2026-124194 is the urgent one, but November's release also fixed several Critical bugs that attackers will study now that patches are public. None of these were exploited at release, but they're worth installing in the same pass:

CVE Product Type Why it matters
CVE-2026-110043 Outlook Remote code execution, Critical, CVSS 8.8 Can be triggered through the Preview Pane with a single click
CVE-2026-110068 Outlook Remote code execution, Critical Another Outlook code execution flaw fixed by the same Office update
CVE-2026-111309 Outlook Remote code execution, Critical Same Office update
CVE-2026-118207 Exchange Server Remote code execution, Critical Only matters if you run Exchange on your own servers
CVE-2026-116928 Windows Search Remote code execution, CVSS 9.8 Flagged by the Zero Day Initiative as needing immediate attention

The good news: the Office update you install for CVE-2026-124194 also covers the Outlook fixes, so one update handles four Outlook bugs at once.

How to Spot an Attack

Detection for this flaw is still early, so treat these as leads to investigate, not proof of an attack:

  • Unexpected outbound connections from Outlook to unknown external servers, especially over SMB (port 445)
  • NTLM authentication events that appear right after a user opens an email attachment or message file
  • Phishing emails with unusual Office attachments, especially from unfamiliar senders or with urgent "review this document" language
  • Sign-ins from new locations shortly after someone opened such a file, which could mean a cracked or relayed credential

If you find something, reset the user's password, check for new sign-ins and mailbox rules, and review what that account can access. Our developer laptop security checklist covers how to protect the devices where these attachments get opened.

November 2026 Patch Tuesday at a Glance

Microsoft released its November 2026 security updates on November 10. According to Tenable's November Patch Tuesday analysis, the release fixed 1,093 vulnerabilities, 63 of them rated Critical. It was Microsoft's second four-figure Patch Tuesday in a row. Counts vary slightly between sources, depending on whether third-party fixes are included.

Only one of those flaws, CVE-2026-124194, was exploited before the patch. That makes the priority list simple for a small business:

  1. Office updates first, for the Outlook zero-day and the Critical Outlook bugs.
  2. Windows updates next, for the Windows Search, Schannel and LDAP fixes.
  3. Exchange Server updates, only if you still run Exchange on your own hardware.
  4. Browsers too. The same week, Chrome patched its own exploited zero-day, CVE-2026-125350, which is also on CISA's list.

This alert is part of our website security for small business guide, which puts every 2026 incident into a layer-by-layer plan you can follow.

Not sure if this affects you? I've recovered 50+ attacked websites. Request a security review.

CVE-2026-124194 FAQs

What is CVE-2026-124194?
CVE-2026-124194 is a spoofing vulnerability in classic Microsoft Outlook, rated CVSS 6.5. When a user opens a crafted Office file, Outlook can leak the user's Windows NTLMv2 hash to an attacker without the warning it should show. Microsoft patched it on November 10, 2026.
Is CVE-2026-124194 being exploited?
Yes. Microsoft says it was exploited in the wild as a zero-day before the patch was released, and CISA added it to its Known Exploited Vulnerabilities catalog on November 10, 2026, with a November 24 deadline for federal agencies. Microsoft hasn't shared who is behind the attacks.
How do I patch the Outlook zero-day?
In Outlook, go to File, then Office Account, then Update Options, then Update Now. Restart Outlook when the update finishes and check that your build matches the fixed version in Microsoft's advisory. In managed organizations, IT deploys the November Office security update centrally.
Does Windows Update fix CVE-2026-124194?
Usually not on its own. Microsoft 365 desktop apps, including Outlook, normally update through Office's own update channel rather than Windows Update. Update Office directly, or confirm your IT team has deployed the November 2026 Office update, even if Windows is fully patched.
Does the new Outlook or Outlook on the web need patching?
The main risk is classic Outlook on Windows. Outlook on the web and the new Outlook for Windows are updated by Microsoft's servers, so there's nothing for you to install. Check Microsoft's advisory for the exact list of affected products to be sure.
What is an NTLM hash, and why does it matter?
An NTLM hash is a scrambled version of your Windows password that Windows uses to prove who you are. Attackers who steal one can try to crack it offline to recover the password, or relay it to other services to log in as you without knowing the password.

Conclusion: Update Office Today, Not Just Windows

CVE-2026-124194 is a "Moderate" bug that attackers are actively using, which makes it the most important fix in November's Patch Tuesday. Open Outlook, update Office, restart it and confirm the build. Then have your IT team block outbound SMB and tighten NTLM to stop the next leak of this kind.

It's one of several patch-now alerts this month. Our website security for small business guide pulls them into one plan. If you'd like help checking that every device and site is patched, see my website security services.

Sources

Get new posts by email
New guides and alerts, sent when they are published. No spam. Unsubscribe anytime.

Comments (0)

Related Blog

APT root flaw CVE-2026-109518 title graphic: a server rack with a package that is half verified and half tampered, linked to a hooded attacker, with the line Patch With Retries Off for Debian 12+ and Ubuntu 22.04+, fixed November 4
Security Alerts
  • 16 Nov 2026
  • <25
  • 0 Comment

APT CVE-2026-109518: Patch Your Debian and Ubuntu Servers Safely

APT CVE-2026-109518 can install a swapped package as root on Debian and Ubuntu. Patch APT with retries off, verify the version and rebuild Docker images.


Meta's 805 million euro fine: how to close Facebook's access to your photo gallery
Security Alerts
  • 15 Nov 2026
  • 359
  • 0 Comment

Meta's €805M Fine: Facebook Was Reading Your Photo Gallery. Here's How to Turn It Off

Italy fined Meta €805M because Facebook read Android photo galleries without clear consent. Turn off gallery access on Android and iPhone in 2 minutes.


WordPress update flaw CVE-2026-119977: block, then update. Exploited now, fixed in WordPress 7.1.4
Security Alerts
  • 14 Nov 2026
  • 75
  • 0 Comment

WordPress CVE-2026-119977: Why Updating Can Expose Your Site

WordPress CVE-2026-119977 is exploited, and the update to 7.1.4 itself can be raced. Block wp-content/upgrade first, then update and verify, step by step.


,