Microsoft Patch Tuesday Fixes Actively Exploited Outlook NTLM Hash Leak Vulnerability
Redmond fixes CVE-2026-124194 alongside 68 critical bugs across Windows and Office as CISA mandates rapid federal deployment to stop silent authentication credential theft.

By Aarav Mehta, Cloud & Enterprise Tech
, updated 6 min read
Microsoft has published its monthly security release addressing 1,252 security vulnerabilities across the Windows operating system, Microsoft Office suite, and cloud developer components, headlined by a patch for an actively exploited zero-day flaw in Microsoft Outlook.
The zero-day vulnerability, tracked as CVE-2026-124194 and assigned a CVSS score of 6.5, allows remote unauthenticated attackers to steal enterprise NTLMv2 authentication hashes by inducing affected clients to initiate outbound SMB connections without user interaction.
The United States Cybersecurity and Infrastructure Security Agency has ordered federal civilian agencies to apply the update within ten business days, warning that sophisticated threat groups are using the flaw to compromise corporate active directory networks and execute lateral movement.
Exploitation Mechanics of CVE-2026-124194
The vulnerability resides in the way Microsoft Outlook handles preview rendering for specially crafted email attachments containing embedded UNC (Universal Naming Convention) path descriptors.
When an attacker sends an email containing a weaponized file object, Outlook attempts to parse associated metadata upon receiving or previewing the message. During this parsing operation, the application automatically initiates an outbound connection over SMB (Server Message Block) port 445 to a remote, attacker-controlled server.
During the SMB negotiation handshake, Windows automatically transmits the authenticated user's NTLMv2 password hash to the external server. Threat actors capture these hashes using public utilities, subsequently cracking them offline or relaying the credentials across internal enterprise systems that have not enforced SMB signing or NTLM deprecation.
Significantly, successful exploitation does not require the victim to click on an attachment, launch an executable file, or preview the message in a full window; processing the raw message header within the preview pane is sufficient to trigger the outbound authentication request.
Critical Remote Code Execution Patches Across Windows Core
Beyond the Outlook authentication leak, Microsoft's security bulletin resolves 68 vulnerabilities classified as Critical, the majority of which involve remote code execution within Windows networking and virtualization sub-systems.
Highlights of the security update include:
Critical RCE fixes in the Windows Hyper-V hypervisor addressing guest-to-host virtual machine escape vulnerabilities that could allow an attacker operating within a tenant container to compromise the physical host.
Patches for Windows Remote Desktop Services resolving pre-authentication memory safety defects that could permit unauthenticated network worms to traverse enterprise networks over port 3389.
Security updates for the Microsoft Windows Kerberos authentication service addressing ticket-forging weaknesses that could allow attackers to escalate privileges from a compromised domain workstation to domain controller authority.
Administrative Hardening and NTLM Deprecation Guidance
Security architects emphasise that while applying the software patch resolves the specific Outlook parsing flaw, enterprises must systematically eliminate organizational reliance on legacy NTLM authentication.
Microsoft has previously announced plans to disable NTLM across future Windows releases in favour of modern Kerberos and public-key authentication mechanisms. However, legacy enterprise applications, internal print servers, and third-party storage appliances frequently perpetuate NTLM usage.
Security teams are urged to implement immediate compensating controls, including:
Blocking outbound SMB traffic (TCP port 445 and UDP ports 137-139) at the enterprise perimeter firewall, preventing internal workstations from transmitting authentication handshakes to external internet IP addresses.
Configuring Windows Group Policy to restrict NTLM usage, enabling audit mode to identify legacy applications that rely on NTLM before enforcing complete protocol blocking.
Enforcing SMB signing and Extended Protection for Authentication (EPA) across all enterprise web and Active Directory services to defeat NTLM relay attacks.
Deployment Verification and Rollout Staging
Given the substantial volume of updates included in the monthly release, IT operations teams are advised to deploy patches through structured deployment rings, verifying application stability on staging systems prior to broad production rollout.
Administrators running cloud-hosted Windows Server virtual machines in Microsoft Azure and AWS can leverage automated patch management tools to stage reboots during scheduled maintenance windows, ensuring core infrastructure remains protected against actively circulating exploit toolkits.
Sources
- 1Microsoft Security Response Centermsrc.microsoft.com