Outlook Zero-Day Was Leaking Password Hashes Before Microsoft's Fix

Microsoft fixed an Outlook bug hackers were already exploiting to steal Windows login hashes, and CISA gave US agencies until Nov 24 to patch.

Nov 18, 2026 - 19:05
4 min read
 0
Outlook Zero-Day Was Leaking Password Hashes Before Microsoft's Fix

If you still use classic Outlook for Windows, a message sitting in your inbox over the past few weeks could have quietly handed a stranger your Windows login credentials, without you clicking a single link. Microsoft has now patched the flaw, but only after it had already been used in real attacks.

A booby-trapped email, not a dodgy link

The bug, tracked as CVE-2026-124194, lives in how classic Outlook for Windows handles certain message files. Researchers found that a specially crafted file could make Outlook quietly reach out to a server the attacker controls, leaking the user's NTLMv2 hash in the process — a scrambled version of your Windows login credentials that the operating system uses internally to prove who you are on a network. Think of it as a locked box that should never leave your machine; this bug mailed the box straight to whoever sent the message. Once attackers have that hash, they can try to crack it offline or relay it to log into other systems on the same network as the victim, often without ever needing the actual password.

Microsoft rates the flaw 6.5 out of 10 on the CVSS severity scale, which sounds almost ordinary. But that number measures how damaging a single exploit is, not how often it gets used — and this one was already being exploited before a fix existed, which is exactly what makes it a genuine zero-day.

Already on the US government's most-wanted list

Microsoft shipped the fix as part of its November Patch Tuesday — the monthly batch of security updates it releases on the second Tuesday of every month — alongside roughly 1,093 other fixes, 63 of them rated critical. The Outlook fix arrives through an Office update rather than the usual Windows Update channel, so if you only click "check for updates" in Windows Settings, you could easily miss it.

The US Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-124194 to its Known Exploited Vulnerabilities catalog — a running list of bugs confirmed to be used in real-world attacks — the same day the patch shipped, and gave US federal civilian agencies until November 24 to apply it.

A patch that arrives after attackers have already found the hole doesn't un-ring the bell — it just stops the bleeding for everyone who hasn't been hit yet.

Practical steps worth taking right away:

  • Open Outlook, go to File → Office Account → Update Options → Update Now to pull the fix manually.
  • Check your build number against Microsoft's advisory for CVE-2026-124194 to confirm the patch has actually installed.
  • If your organisation manages updates centrally through WSUS or Intune, verify the November Office security update has actually been pushed — don't assume a general Patch Tuesday rollout covered it.

Why this matters for India specifically

CISA's November 24 deadline only legally binds US federal agencies, but the vulnerability itself doesn't respect borders. India has one of the largest enterprise user bases for Outlook and Microsoft 365 anywhere in the world, running everything from bank back-offices to government ministries on it, so the real-world exposure here is arguably just as large as in the US. CERT-In, India's Computer Emergency Response Team under the Ministry of Electronics and IT, routinely issues its own advisories pointing back to Microsoft's Patch Tuesday releases, and this is exactly the kind of bug — already exploited, delivered outside the usual Windows Update flow, easy to overlook — that tends to sit unpatched in Indian enterprises for months after a fix exists. Last month's record-breaking Patch Tuesday showed the same pattern: a live zero-day shipped alongside a record patch batch, and the fix is only as good as how quickly IT teams actually roll it out.

The pattern repeating every month

This is now the second month running that Microsoft's Patch Tuesday has included a zero-day that was already being exploited before the fix landed. That's less a coincidence than a reflection of how attackers operate today: find a quiet corner of a widely used product, use it sparingly against high-value targets, and keep using it until someone notices. The fix for any single Patch Tuesday is simple enough — install the update. The harder problem, for IT teams everywhere including in India, is building the habit of treating these monthly releases as urgent rather than routine, because by the time a vulnerability makes the news, someone has usually already been hit by it.

Short URL: https://code24.in/2e2c8b25

What's Your Reaction?

Like Like 0
Dislike Dislike 0
Love Love 0
Funny Funny 0
Angry Angry 0
Sad Sad 0
Wow Wow 0
Ashif Sadique As an full-stack developer, I'm passionate about sharing tutorials and tips that aid other programmers. With expertise in PHP, Python, Laravel, Angular, Vue, Node, Javascript, JQuery, MySql, Codeigniter, and Bootstrap. To me, consistency and hard work are the keys to success.