CVE-2026-124194: Patch Outlook and Block NTLMv2 Hash Leaks

Outlook message file credential leak blocked by an outbound firewall

Microsoft says CVE-2026-124194 is being exploited in the wild. The Outlook flaw can make a user-opened message file contact an attacker-controlled network location without the usual external-content warning, exposing the user’s NTLMv2 hash. The November 10, 2026 security update is the primary fix. Egress controls and NTLM restrictions reduce the blast radius, but they do not replace patching.

This guide explains what the vulnerability does, who should act first, how to validate Outlook patch coverage, and how to test an SMB client control in an isolated Windows lab. It does not include exploit code or a weaponized message file.

What Microsoft disclosed

Microsoft’s security advisory classifies CVE-2026-124194 as an Outlook spoofing vulnerability and assigns a CVSS 3.1 base score of 6.5. The score can look modest beside a remote-code-execution bug, but the operational context is more urgent: Microsoft marks exploitation as detected and an official fix as available.

The attack requires an unauthenticated adversary to deliver a specially crafted message file and persuade the recipient to open it in an affected Outlook version. Microsoft explicitly says the Preview Pane is not an attack vector. Once the file is opened, Outlook can connect to an attacker-controlled network location without the normal warning and disclose the user’s NTLMv2 hash. That hash may then support impersonation or relay activity where other controls permit it.

Key facts for triage

  • Disclosure date: November 10, 2026.
  • Product: affected versions of Microsoft Office Outlook, including Microsoft 365 Apps for Enterprise and supported Office LTSC releases listed by Microsoft.
  • Attack path: a malicious message file opened by the user.
  • Security impact: disclosure of the user’s NTLMv2 hash, with high confidentiality impact in Microsoft’s assessment.
  • Preview Pane: not an attack vector, according to Microsoft.
  • Status: exploitation detected; official security updates are available.

CISA also lists the vulnerability in its Known Exploited Vulnerabilities Catalog. For organizations that follow KEV as a prioritization signal, that moves CVE-2026-124194 out of the routine monthly queue and into an accelerated remediation track.

Why an Outlook credential leak matters

NTLM authentication is still present in many Windows estates because old applications, workgroup systems, appliances, and cross-boundary workflows depend on it. A leaked NTLMv2 challenge-response value is not the same as a cleartext password, but it is still valuable to an attacker. Depending on password strength and the surrounding environment, an operator may attempt offline cracking or relay the authentication to a service that accepts NTLM without adequate protections.

The dangerous part of this Outlook bug is the combination of a trusted desktop client, a user-opened file, and an outbound authentication attempt that can cross a network boundary. Email filtering can reduce delivery, but defenders should assume that some files will reach endpoints through webmail, collaboration tools, browser downloads, archives, or removable media.

This also means that a successful patch program needs two measurements: whether Outlook received the security update and whether endpoints can still send SMB or NTLM authentication to untrusted destinations. The first closes the specific flaw. The second limits similar credential-coercion paths and provides resilience against future bugs.

Immediate response plan

1. Patch affected Outlook installations

Use your normal Microsoft 365 Apps, Configuration Manager, Intune, WSUS, or Office deployment workflow to install the November 2026 security updates for the affected channel and release. Do not assume that a successful Windows cumulative update proves Office is current. Click-to-Run Microsoft 365 Apps and perpetual Office builds can follow different servicing paths.

Compare the installed Outlook version against the fixed build shown for your product in the Microsoft Security Update Guide. Microsoft’s affected-product table is the authority because channel build numbers can change as updates are revised.

2. Prioritize exposed user groups

Start with users who regularly handle unsolicited attachments, shared mailboxes, external support requests, recruiting submissions, financial documents, and incident reports. Include administrators who read mail from privileged workstations. A credential leak from a highly privileged session can be more consequential than the same event on a restricted endpoint.

3. Restrict outbound SMB

Microsoft recommends blocking outbound TCP 445 to the internet unless a documented service requires it. Apply the control at network egress and on mobile endpoints that may operate away from the corporate firewall. Review exceptions carefully for Azure Files or other approved SMB services and prefer private connectivity where practical.

4. Reduce NTLM dependence

On supported systems, SMB client NTLM blocking can stop the client from falling back to NTLM for remote outbound connections. Microsoft’s current guidance documents the control for Windows 11 version 24H2 and Windows Server 2025. Older Windows versions need different policy planning, so do not push an unsupported command broadly.

Before enforcement, inventory legacy file shares and applications, stage the change with a small pilot group, and document required exceptions. The related VigilSecureInfo guide, Audit NTLM Signing Before Enforcement, provides a complementary workflow for finding dependencies before tightening policy.

Detection and investigation

Microsoft’s public advisory describes the vulnerable behavior, but it does not publish a complete set of incident indicators. Treat detection as behavioral analysis rather than a single filename or hash match.

Hunt for the delivery and the network action

  • Search email, endpoint, proxy, and download telemetry for message files opened from unusual locations, especially user-writable directories, archives, browser download folders, and collaboration caches.
  • Review outbound TCP 445 attempts from user workstations to public IP addresses. Any such traffic deserves validation even when the connection failed.
  • Correlate Outlook process activity with subsequent SMB client connections, authentication attempts, or name-resolution lookups to domains not previously seen in the environment.
  • Look for clustered delivery to several users, similar filenames, common sender infrastructure, and repeated destination hosts.
  • On a suspected endpoint, preserve the original file, email headers, Outlook and endpoint telemetry, DNS evidence, firewall logs, and the user’s recent authentication history before cleanup.

Do not equate a blocked outbound connection with a harmless event. A failed SMB connection can still confirm that a user opened the lure and may help identify other recipients. If authentication reached an untrusted host, reset the user’s password, invalidate relevant sessions, review privileged group membership, and investigate possible NTLM relay or lateral movement.

Useful SOC correlations

A practical correlation starts with an Outlook child or associated file-open event, then searches a short time window for public-destination SMB traffic from the same device. Add identity telemetry for the same account and destination. Tune out approved file-service ranges rather than excluding all port 445 traffic. Keep the analytic transparent: analysts should be able to see which file, process, device, account, and destination caused the match.

Hands-on lab: validate Outlook inventory and SMB NTLM blocking

This defensive lab uses a disposable Windows 11 24H2 or Windows Server 2025 virtual machine. It does not reproduce CVE-2026-124194. It validates two controls that matter during response: reliable Outlook version inventory and SMB client NTLM blocking.

Prerequisites

  • A disposable Windows 11 24H2 or Windows Server 2025 VM with a snapshot.
  • Local administrator access.
  • Microsoft Outlook installed for the inventory step.
  • No production file-share dependency on the test VM.

Step 1: collect the installed Outlook version

Open PowerShell and run:

$candidates = @(
  "$env:ProgramFiles\Microsoft Office\root\Office16\OUTLOOK.EXE",
  "${env:ProgramFiles(x86)}\Microsoft Office\root\Office16\OUTLOOK.EXE"
)

$outlook = $candidates | Where-Object { Test-Path $_ } | Select-Object -First 1

if (-not $outlook) {
  Write-Warning "Outlook executable not found in the standard Click-to-Run paths."
} else {
  Get-Item $outlook | Select-Object FullName, @{
    Name = "FileVersion"
    Expression = { $_.VersionInfo.FileVersion }
  }
}

Expected output: the full path to OUTLOOK.EXE and a numeric file version. If the script does not find Outlook, query your Office deployment inventory or adapt the path for an MSI-based installation. Compare the result with Microsoft’s affected-product and fixed-build table. Do not compare against a build copied from a third-party summary.

Step 2: record the current SMB client setting

$before = Get-SmbClientConfiguration
$before | Select-Object BlockNTLM, EnableSecuritySignature, RequireSecuritySignature

Expected output: a row showing the current Boolean values. Keep the PowerShell session open so the cleanup step can restore the original BlockNTLM state.

Step 3: enable SMB client NTLM blocking in the lab

Set-SmbClientConfiguration -BlockNTLM $true -Confirm:$false
Get-SmbClientConfiguration | Select-Object BlockNTLM

Expected output: BlockNTLM is True. This setting prevents the SMB client from using LM, NTLM, or NTLMv2 for remote outbound connections. Kerberos-capable file services can continue to work when identity and name resolution are configured correctly.

Microsoft documents this control in Block NTLM connections on SMB. Test business workflows before deployment because legacy or non-domain file servers may rely on NTLM.

Troubleshooting

  • If BlockNTLM is not a recognized property, confirm the VM is Windows 11 24H2 or Windows Server 2025 and fully updated.
  • If an approved file share fails after the change, verify that the client uses the server’s correct DNS name and that Kerberos is available. Do not immediately create a broad exception.
  • If Outlook is installed through a nonstandard path, use your endpoint-management inventory rather than searching the whole disk during an incident.

Cleanup

Set-SmbClientConfiguration -BlockNTLM $before.BlockNTLM -Confirm:$false
Get-SmbClientConfiguration | Select-Object BlockNTLM

Expected output: the setting matches the value captured in Step 2. Revert the VM snapshot if you made any other lab changes.

Hardening after the emergency patch

Once patch coverage is confirmed, keep the controls that make credential-coercion attacks harder. Block internet-bound SMB at every egress point, reduce NTLM use, require SMB signing where appropriate, separate daily email use from privileged administration, and monitor authentication from unmanaged or unexpected hosts.

Microsoft 365 teams should also confirm that baseline configuration is measurable across the tenant. The VigilSecureInfo guide CISA ScubaGear 2.0: Audit Microsoft 365 Security Baselines shows how to make that review repeatable rather than relying on screenshots and one-time checks.

Response checklist

  1. Confirm affected Outlook products and servicing channels.
  2. Deploy the November 2026 security update and verify installed versions.
  3. Prioritize attachment-heavy and privileged user groups.
  4. Block outbound TCP 445 to untrusted networks.
  5. Pilot SMB client NTLM blocking on supported Windows systems.
  6. Hunt for message-file opens followed by public-destination SMB activity.
  7. Reset credentials and investigate relay risk when authentication reached an untrusted host.
  8. Preserve evidence before deleting files or rebuilding endpoints.

Conclusion

CVE-2026-124194 is a reminder that a user-opened email file can become an identity event, not just an endpoint event. Patch Outlook first, then verify that the network and authentication layers can contain the same failure mode. Teams that measure Office versions, block unneeded outbound SMB, and reduce NTLM dependence will be better positioned for this incident and the next credential-coercion flaw.

References

Similar Posts