Summary
CVE-2026-124194 is a Microsoft Outlook flaw that can expose a user’s NTLMv2 hash. An attacker sends a malicious Office file and tricks the victim into opening it in Outlook. Outlook then connects to an attacker-controlled location without showing a warning, potentially exposing the user’s hash and allowing impersonation.
The vulnerability requires user interaction and network connectivity. Opening the malicious file is necessary for the attack; the Preview Pane is not an attack vector.
Urgent Actions Required
- Apply Microsoft's security updates for the affected Office products. For Office LTSC 2021, update to build 16.0.14334.21048 or later. For Office LTSC 2024, update to build 16.0.17932.21140 or later.
- Check Microsoft 365 Apps for Enterprise updates against Microsoft's published security release information to confirm that the installed version is no longer affected.
- Prioritize remediation. CISA has added this vulnerability to its Known Exploited Vulnerabilities (KEV) Catalog, with a remediation deadline of November 24, 2026.
Which Systems Are Vulnerable to CVE-2026-124194?
Technical Overview
- Vulnerability Type:Missing User Interaction for Potentially Unsafe Action (CWE-356), leading to spoofing in Microsoft Office Outlook.
- Affected Software/Versions:
- Microsoft 365 Apps for Enterprise: Version 16.0.1 and earlier within the affected release range.
- Microsoft Office LTSC 2021: Versions 16.0.1 to below 16.0.14334.21048.
- Microsoft Office LTSC 2024: Versions 16.0.0 to below 16.0.17932.21140.
- Attack Vector:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: Required
- Scope: Unchanged
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
- Patch Availability: Yes, available
How Does the CVE-2026-124194 Exploit Work?
The attack typically follows these steps:
What Causes CVE-2026-124194?
Vulnerability Root Cause:
CVE-2026-124194 is caused by Microsoft Outlook failing to display a warning before performing a potentially unsafe network action. When a user opens a specially crafted malicious Office file, Outlook connects to an attacker-controlled network location without showing the usual external-content warning. This can expose the user’s NTLMv2 hash, which an attacker may use to authenticate as or impersonate the victim.
How Can You Mitigate CVE-2026-124194?
If immediate patching is delayed or not possible:
- Avoid opening suspicious Office files received from untrusted sources.
- Remind users not to open unexpected or unverified Office attachments in Outlook.
- Prioritize affected Outlook installations for security updates.
- Review affected Office versions and follow Microsoft’s security update guidance.
Which Assets and Systems Are at Risk?
- Asset Types Affected:
- Microsoft Office Applications: Microsoft 365 Apps for Enterprise, Office LTSC 2021, and Office LTSC 2024.
- Outlook Users: Users who open specially crafted malicious Office files in affected Outlook versions.
- Business-Critical Systems at Risk:
- Enterprise Email Environments: Outlook installations that may process malicious Office files.
- User Accounts: NTLMv2 hash exposure could allow attackers to impersonate affected users.
- Systems Running Affected Office Versions: Unpatched installations remain exposed to this actively exploited vulnerability.
- Exposure Level:
- Affected Office Installations: Systems running the vulnerable Microsoft 365 Apps or Office LTSC versions.
- Network-Connected Systems: Exploitation requires network connectivity and user interaction.
- Unpatched Environments: Organizations using affected versions should prioritize Microsoft's security updates.
How Can You Detect CVE-2026-124194 Exploitation?
Exploitation Signatures:
- Outlook opening a specially crafted malicious Office file.
- Outlook making an unexpected connection to an attacker-controlled network location without displaying the usual external-content warning.
- Unexpected exposure of a user’s NTLMv2 hash.
Indicators of Compromise (IOCs/IOAs):
- Suspicious Office files received from untrusted sources.
- Unexpected Outlook connections to external network locations.
- Evidence of NTLMv2 hash disclosure associated with Outlook activity.
Alerting Strategy:
- Priority: High
- Monitor for unusual outbound network connections initiated by Outlook.
- Investigate suspicious Office files opened by users.
- Prioritize alerts involving unexpected Outlook network connections and potential NTLMv2 hash exposure.
Remediation & Response
- Remediation Timeline:
- Immediate: Prioritize security updates for affected Microsoft Outlook installations because the vulnerability is actively exploited.
- By November 24, 2026: Complete remediation in line with the CISA KEV deadline.
- After Updates: Verify that affected Office installations are running fixed builds.
- Incident Response Considerations:
- Investigate suspicious Office files opened in affected Outlook installations.
- Review unusual network connections initiated by Outlook to identify possible connections to attacker-controlled locations.
- Assess whether users' NTLMv2 hashes may have been exposed.
- Follow Microsoft's security update guidance and CISA's remediation requirements.
- Apply CISA's applicable forensic triage requirements for vulnerabilities listed in its KEV Catalog.
Compliance & Governance Notes
- Audit Trail Requirement:
- Record the security updates applied to affected Microsoft Office installations.
- Maintain details of patched products and their installed versions.
- Document remediation progress to demonstrate compliance with applicable CISA requirements.
- Track remediation against the CISA KEV deadline of November 24, 2026.
Get deeper network visibility and faster threat detection with Fidelis NDR
-
-
- Understand threats across all ports and protocols
- Explore deep session inspection, network DLP, and sandboxing
- Discover automated threat detection, hunting, and network forensics
- Learn how threat intelligence and deception strengthen network security
-
CVSS Breakdown Table
| Metric | Value | Description |
|---|---|---|
| Base Score | 6.5 | Indicates a vulnerability with significant confidentiality impact and moderate overall severity |
| Attack Vector | Network | The attacker can exploit the vulnerability over a network |
| Attack Complexity | Low | Exploitation does not require special conditions or complex procedures |
| Privileges Required | None | The attacker does not need prior authentication or elevated privileges |
| User Interaction | Required | The victim must open a specially crafted malicious Office file in Outlook |
| Scope | Unchanged | The impact remains within the security authority of the vulnerable component |
| Confidentiality Impact | High | Successful exploitation can expose the victim's NTLMv2 hash |
| Integrity Impact | None | The documented attack exposes the user's NTLMv2 hash but does not involve modifying or tampering with data |
| Availability Impact | None | The exploitation method does not disrupt Outlook services or affect system availability |
References: