Microsoft's 10 November 2026 release closed an actively exploited Outlook flaw. A single opened message file hands the user's NTLMv2 authentication hash to the attacker.
With its monthly security release on 10 November 2026, Microsoft closed an Outlook flaw that attackers had already been using before any fix existed. The vulnerability, tracked as CVE-2026-124194, causes Outlook to quietly connect to a network location of the attacker's choosing when a specially crafted message file is opened. The usual external-content warning never appears, and Windows hands the attacker's server the user's NTLMv2 authentication hash.
According to BleepingComputer, the same release fixed 1,235 vulnerabilities in total, making it the largest single batch of patches Microsoft has ever shipped. Within that pile, CVE-2026-124194 carries a CVSS score of only 6.5, which does not even qualify as critical. Even so, the US cybersecurity agency CISA added it to the Known Exploited Vulnerabilities (KEV) catalog and set 24 November 2026 as the patching deadline for federal agencies.
Why the low score is misleading
The score stays low for two reasons: the attack requires the user to open the file, and the direct impact is classified as information disclosure. In practice the picture looks different. The leaked NTLMv2 hash is not a plaintext password, but an attacker can relay it to another service on the network and authenticate as that user, or attempt to crack it offline to recover the password. A single opened file therefore does not stay confined to one mailbox; it opens a path for lateral movement inside the company network. Microsoft's own advisory notes that the disclosed information could let an attacker authenticate as the user.
The flaw affects the classic Outlook client on Windows. That is exactly the setup a typical small or mid-sized office runs: domain-joined Windows machines, a local file server and desktop Outlook. If a privileged account or a finance staff member opens the wrong attachment, the attacker gains a foothold to move further.
There is a regulatory side to this as well. If systems holding personal data are reached this way, the incident becomes a data breach under Turkey's Law No. 6698. Under decision 2019/10 of the Personal Data Protection Board, the data controller must notify the Board within 72 hours of becoming aware of the breach. Delaying a patch creates administrative exposure, not just technical risk.
What we recommend at Kamer Bilişim
- Patch the Office clients first. Server patches can usually wait for a maintenance window; Outlook cannot. Confirm that the Microsoft 365 Apps update channel is genuinely working and check Office build numbers machine by machine. Automatic updates being enabled does not guarantee they are current.
- Stop NTLM from leaving the network. Block outbound ports 445 and 139 at the firewall, enforce SMB and LDAP signing on domain controllers, and move administrator accounts into the Protected Users group. Together these three settings remove the destinations an attacker would need, even if a hash is captured.
- Look backwards at the pre-patch window. A patch closes the hole; it does not recall a hash that already left. Filter inbound .msg and .eml attachments at the mail gateway, reset passwords for anyone who opened a suspicious file, and review authentication logs for that period.
All three steps depend on treating patch tracking and firewall configuration as a routine process rather than an occasional task. For clients on a corporate maintenance agreement, we run the patch cycle and the NTLM hardening on their behalf. If you would like to review where your network stands against this flaw, reach us through our contact page.
Source: BleepingComputer, "Microsoft November 2026 Patch Tuesday fixes 1,235 flaws, Outlook zero-day", 10 November 2026; CISA Known Exploited Vulnerabilities Catalog; Turkish Personal Data Protection Board decision 2019/10.
Source: BleepingComputer