One Opened Outlook File Can Leak a Windows Login

Outlook zero-day CVE-2026-124194 leaks Windows login hashes from one opened file; here's how to patch and lock down your clients' PCs.

A single message file, opened in Outlook, can quietly hand a scrambled copy of the reader's Windows login to an attacker's server, with no external-content warning. Microsoft patched CVE-2026-124194 on 10 November 2026 and says attackers are already exploiting it. Check every client's Office build today, because this fix arrives as an Office update.

TL;DR

  • Microsoft fixed Outlook zero-day CVE-2026-124194 on 10 November 2026; CISA lists it as exploited, with a 24 November 2026 federal deadline.
  • A client is exposed if Microsoft 365 Apps for Enterprise, Office LTSC 2021 or Office LTSC 2024 runs below the 10 November builds in Microsoft's Office security release notes.
  • Update Office on every PC, block outbound TCP 445 to the internet as Microsoft advises, and reset passwords for users whose PCs reached outside SMB servers.
  • SecurityWeek reports the leaked NTLMv2 hash lets an attacker authenticate as that user.

What is CVE-2026-124194 and is it being exploited?

CVE-2026-124194 is a spoofing flaw in Microsoft Outlook: the program fails to warn the user before an unsafe action, per the CVE record. Microsoft says it is being exploited, and CISA added it to its Known Exploited Vulnerabilities list on 10 November 2026, due 24 November 2026 for federal agencies.

Microsoft rates it "Moderate"; NVD lists 6.5 (CVSS). According to SecurityWeek, the victim must open a crafted message file; the Preview Pane is not a trigger. Outlook then contacts an attacker's server and leaks the user's NTLMv2 hash, a scrambled form of the Windows login. The Hacker News reports Microsoft has named no threat actor.

Which Office versions are affected?

The CVE record lists Microsoft 365 Apps for Enterprise, Office LTSC 2021 and Office LTSC 2024, in 32-bit and 64-bit editions.

Product Branch Fixed in
Microsoft 365 Apps Current Channel 2610 20527.20196
Microsoft 365 Apps Monthly Enterprise 2610 / 2609 / 2608 20527.20194 / 20430.20264 / 20326.20320
Microsoft 365 Apps Semi-Annual Enterprise 2610 / 2609 / 2608 20527.20192 / 20430.20262 / 20326.20318
Office LTSC 2024 2408 17932.21140
Office LTSC 2021 2108 14334.21048

Fixed builds from Microsoft's release notes for Office security updates.

How do I check if my clients are exposed to CVE-2026-124194?

Microsoft has published no indicators and no first-exploitation date, so search the oldest retained logs; earlier activity can't be ruled out. Run the PowerShell as an administrator.

  1. Preserve evidence. Export each PC's NTLM and Security event logs with wevtutil, hash them, and export the perimeter firewall's traffic logs from its console. Pass: the .sha256 file lists both .evtx files.

    $D = "C:\IR\$env:COMPUTERNAME"; New-Item -ItemType Directory -Force $D | Out-Null
    wevtutil epl Microsoft-Windows-NTLM/Operational "$D\ntlm.evtx"
    wevtutil epl Security "$D\security.evtx"
    Get-FileHash "$D\*.evtx" -Algorithm SHA256 | Out-File "$D.sha256"
    
  2. Read every PC's Office build. This reads VersionToReport, the installed Office build, from the Click-to-Run registry key. Pass: each build's last two parts match or exceed its channel's row in the table.

    # client-pcs.txt: one hostname per line, from the client's asset inventory
    # an error on a PC means no Click-to-Run Office there; check that PC by hand
    Invoke-Command -ComputerName (Get-Content .\client-pcs.txt) -ScriptBlock { [pscustomobject]@{ Host = $env:COMPUTERNAME; Build = (Get-ItemPropertyValue 'HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration' -Name VersionToReport) } }
    
  3. Confirm outbound SMB is blocked. SMB is Windows file sharing, and the hash leaks over it. This lists Windows Firewall outbound block rules covering port 445; also open the perimeter firewall's rule list. Pass: both show a block on outbound TCP 445.

    Get-NetFirewallRule -Direction Outbound -Action Block -Enabled True | Get-NetFirewallPortFilter | Where-Object RemotePort -contains '445'
    
  4. Search firewall logs for outbound SMB to the internet. A hit means a PC tried to reach an outside SMB server: treat that user's hash as leaked. Pass: no output.

    # field names vary by firewall vendor (dpt=, dstport=, dst_port=); adjust to match the export
    # add the client's own public ranges to the second grep
    zgrep -hE '(dpt|dstport|dst_port)=(445|139)\b' ./firewall-export/* | grep -vE '(dst|DST)=(10\.|192\.168\.|172\.(1[6-9]|2[0-9]|3[01])\.)'
    

How do I fix CVE-2026-124194 on client PCs?

Patch first, then cut off any leaked logins.

  1. Install the 10 November Office build. Push it through each client's usual Office update path (Intune, Configuration Manager or Office's own automatic updates). Pass: rerun check 2; every build meets its table row.

  2. Block outbound SMB. On the perimeter firewall, block outbound TCP 445 and 139 and UDP 137 and 138, per Microsoft. This can break Azure Files or a home user's NAS. Then add a host rule so laptops stay covered off-site. Pass: rerun check 3; the rule is listed.

    New-NetFirewallRule -DisplayName 'Block SMB to Internet' -Direction Outbound -Protocol TCP -RemotePort 445,139 -RemoteAddress Internet -Action Block
    
  3. Reset leaked logins. For each user flagged by check 4, reset the Active Directory password with Set-ADAccountPassword. Pass: signing in with the old password fails.

    Set-ADAccountPassword -Identity <samAccountName> -Reset -NewPassword (Read-Host -Prompt 'New password' -AsSecureString)
    
  4. Hardening (agree with the client first). Set "Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers" to Audit all under Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options, per Microsoft. Move to Deny all with server exceptions only after review, because apps that still need NTLM will fail. Pass: the command prints audit events.

    Get-WinEvent -LogName Microsoft-Windows-NTLM/Operational -MaxEvents 20
    
  5. Rerun the checks. Pass: checks 2, 3 and 4 all pass.

Why does one Outlook bug matter in a huge Patch Tuesday?

The November 2026 Patch Tuesday fixed so many flaws that one exploited Outlook bug is easy to miss. SecurityWeek counts 1,094 fixes, and The Hacker News counts 1,259 including 165 republished third-party CVEs. The same pattern played out in October's record release. SecurityWeek adds that the credited finders are a researcher called "nono" and Benoît Sevens, whose acknowledgment mentions Anthropic's Claude.

Where KinoSec fits

KinoSec's autonomous Active Directory pentest checks what an attacker on each client's internal network could reach in their domain, which is where a stolen NTLMv2 hash gets used. A leaked hash is only worth as much as the paths it opens, such as certificate templates that turn one login into domain admin. KinoSec does not inventory Office builds on PCs, so checks 2 and 3 cover that part. Use autonomous internal network and Active Directory pentesting for your clients to find those paths and hand each client a report with fixes, on demand rather than once a year.

Frequently Asked Questions

Does the Outlook Preview Pane trigger CVE-2026-124194?

No. According to SecurityWeek, the Preview Pane is not a trigger. The user must open a specially crafted message file. A user who opened an unexpected attachment on an unpatched PC should be treated as possibly affected.

How do I check if my clients were hit by the Outlook NTLM hash leak?

Read VersionToReport under HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration on each PC and compare it with Microsoft's 10 November builds. Then list outbound block rules with Get-NetFirewallRule -Direction Outbound -Action Block. Finally, search exported firewall logs with zgrep -hE '(dpt|dstport)=(445|139)' ./firewall-export/*. Any hit means treat that user's hash as leaked.

What if a client can't block outbound SMB because they use Azure Files?

Microsoft says outbound SMB to the internet is rarely needed except for services such as Azure Files and Office 365. For Azure Files, Microsoft advises sending that traffic over a VPN so outbound SMB is limited to the service's IP ranges. Everything else can then be blocked.

Should my clients treat a "Moderate" rating as low priority?

No. Microsoft says CVE-2026-124194 is exploited, and CISA set a 24 November 2026 deadline for federal agencies. According to The Hacker News, watchTowr's Jake Knott advises patching what faces the internet first, then anything already exploited in the wild, then everything else. This flaw belongs in that second group.