Skip to content
eastbaycyber

CVE-2026-124194: Outlook Spoofing Vulnerability

CVSS · Medium
6.5
In CISA KEV
Yes
Published
Nov 14
Patch SLA & TriageVector: Network
Immediate (BOD 22-01 due 2026-11-24)

Active exploitation confirmed in CISA KEV.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 6.5
Decode Vector & Sub-Scores →
CVE explainers 10 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-14
⚠
CISA Known Exploited Vulnerability

Active exploitation confirmed in the wild. CISA added this to the KEV catalog on 2026-11-10. Federal agencies must patch by 2026-11-24.

Everything CISA added on 2026-11-10 · Microsoft KEV history

▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-124194 is a network-based Microsoft Outlook spoofing vulnerability with a CVSS score of 6.5. - Microsoft 365 Apps for Enterprise and Office LTSC 2021 and 2024 are affected; fixed builds are available. - CISA lists the vulnerability as actively exploited, with a federal remediation deadline of November 24, 2026. - The available reporting suggests possible NTLM credential exposure, but administrators should confirm the attack chain against Microsoft’s complete advisory.

Summary

CVE-2026-124194 is a Microsoft Outlook vulnerability caused by insufficient user warning before a potentially unsafe action. According to the NVD description, an unauthorized attacker can perform spoofing over a network. CISA classifies it as the Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability.

CISA added the vulnerability to its Known Exploited Vulnerabilities (KEV) catalog on November 10, 2026. That status indicates confirmed exploitation in the wild. CISA’s remediation due date is November 24, 2026. The catalog does not identify a known ransomware campaign for this CVE; that field is listed as unknown.

Field Value
CVE ID CVE-2026-124194
Vendor Microsoft
Product Microsoft Office Outlook / Office
CVSS base score 6.5, medium
Attack vector Network
Authentication or privileges required None indicated by the secondary CVSS context
User interaction Required
Patch available Yes
CISA KEV status Yes
CISA date added November 10, 2026
CISA remediation deadline November 24, 2026
Known ransomware campaign Unknown

The authoritative NVD data supplied for this record includes the 6.5 score but does not include a CVSS vector string. A secondary source attributes the vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N; defenders should treat that vector as contextual until verified against the complete Microsoft advisory or NVD record.

Analyst’s Take: Treat the CISA KEV listing as the deciding factor for priority. The CVSS score is medium and user interaction is required, but confirmed exploitation and the November 24, 2026 remediation deadline make patch verification more urgent than waiting for a fully documented exploit chain.

AnalystImpact · assess the risk

Root Cause

The root cause is a missing or inadequate user-interaction warning in Outlook. The interface does not sufficiently alert the user before a potentially unsafe action is performed. An attacker who can reach the target over the network may then induce or exploit a spoofing-related action without the expected safety control.

The supplied authoritative material does not describe the vulnerability as a generic authentication bypass or remote code execution flaw. The documented impact is spoofing, while secondary reporting suggests that exploitation may involve disclosure or coercion of NTLM authentication material. Validate that NTLM-related behavior against Microsoft’s complete advisory and incident-response evidence before treating it as the definitive technical attack chain.

Users may interact with malicious content or attacker-controlled resources through Outlook. The secondary CVSS context assigns high confidentiality impact, but no integrity or availability impact. Monitoring should therefore cover unexpected outbound authentication, suspicious Outlook-triggered network connections, and signs of credential exposure.

Organizations can also review related defensive concepts in the intrusion prevention system glossary and symmetric encryption glossary.

Who’s Exposed

The available references identify the following Microsoft product families as affected:

Product Affected versions Fixed version or guidance
Microsoft 365 Apps for Enterprise A complete authoritative version range was not available in the supplied material Install the applicable Microsoft 365 servicing-channel security build identified in Microsoft’s advisory
Microsoft Office LTSC 2021 A complete affected range was not available in the supplied material; installations below the fixed build should be treated as exposed 16.0.14334.21048 or later
Microsoft Office LTSC 2024 A complete affected range was not available in the supplied material; installations below the fixed build should be treated as exposed 16.0.17932.21140 or later

Both 32-bit and 64-bit Windows editions are referenced in secondary coverage. Because the supplied references do not establish complete authoritative lower and upper version boundaries, asset owners should not infer that a build is safe merely because it is not listed in the table. Compare the installed Office build with Microsoft’s advisory and the applicable November 10, 2026 security update.

Secondary reporting states that New Outlook for Windows, Outlook on the web, Outlook for Mac, and Outlook mobile applications were not listed as affected in the referenced advisory. Check that exclusion against the current Microsoft advisory before using it to close an exposure investigation. Inventory Office edition, architecture, update channel, installed build, and whether classic Outlook is present.

Technical Notes

For Click-to-Run installations, collect the installed Office build from the endpoint rather than relying only on software inventory labels. A PowerShell check can identify common Click-to-Run configuration data:

$paths = @(
  "HKLM:\SOFTWARE\Microsoft\Office\ClickToRun\Configuration",
  "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Office\ClickToRun\Configuration"
)

foreach ($path in $paths) {
  if (Test-Path $path) {
    Get-ItemProperty -Path $path |
      Select-Object PSPath, ProductReleaseIds, ClientVersionToReport, Platform, CDNBaseUrl
  }
}

Treat builds below 16.0.14334.21048 for Office LTSC 2021 and below 16.0.17932.21140 for Office LTSC 2024 as requiring remediation. For Microsoft 365 Apps for Enterprise, map the endpoint to its servicing channel and compare the reported build with the channel-specific fixed build in the Microsoft advisory.

Severity Breakdown

CVE-2026-124194 has an NVD CVSS base score of 6.5, rated medium. The supplied NVD response did not include the authoritative vector string. A secondary search result attributes AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N, which provides useful interpretation but should not replace the official vector.

Component Secondary-source value Practical meaning
Attack vector Network The attacker does not need local access to the endpoint
Attack complexity Low No unusual conditions are indicated in the secondary vector
Privileges required None The attacker does not need an existing account according to the secondary context
User interaction Required A user must take an action or interact with content
Scope Unchanged The impact remains within the vulnerable security authority
Confidentiality High Disclosure of sensitive information is the principal scored impact
Integrity None No direct data modification is scored
Availability None No service disruption is scored

The score should not be used to defer remediation. CVSS describes technical severity under a defined model; it does not incorporate the operational significance of confirmed exploitation. CISA KEV status changes the priority calculation because exploitation has already been observed in the wild.

User interaction also does not make the issue low risk in environments where Outlook users routinely process external email, calendar invitations, links, attachments, or other attacker-controlled content. Combine the CVSS interpretation with email exposure, endpoint criticality, credential privileges, and evidence of suspicious authentication activity.

Exploitation Status

Exploitation in the wild is confirmed through the CISA KEV listing. CVE-2026-124194 was added to the catalog on November 10, 2026, and carries a remediation deadline of November 24, 2026. Handle this as an exploited vulnerability, not as a theoretical or merely anticipated threat.

The CISA record identifies the ransomware campaign field as unknown. No ransomware association is established in the supplied record; that does not mean exploitation is benign or limited. Available reporting also suggests that exploitation may involve NTLM-related credential disclosure or coercion, but that detail requires validation against Microsoft’s complete advisory and primary incident-response reporting.

A public proof of concept is not independently verified in the supplied material. Search results reference an aggregation repository claiming a verified proof of concept and two PoCs, but no independently validated exploit repository or primary researcher report was retrieved. Uncertainty about PoC availability should not reduce urgency. KEV inclusion is sufficient to justify emergency patching and retrospective hunting.

Sources

The primary source is Microsoft’s Security Response Center advisory for CVE-2026-124194:

The NVD record provides the vulnerability description and CVSS score:

CISA’s Known Exploited Vulnerabilities catalog establishes confirmed exploitation, the date added, and the remediation deadline:

Additional secondary references used for product-build context and exploitation reporting include:

Because the Microsoft advisory is dynamically rendered and the supplied NVD response lacks a vector string, administrators should verify affected ranges, channel-specific builds, mitigations, and the authoritative CVSS vector directly against the current Microsoft and NVD records before finalizing change-control documentation.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

ResponderRunbook · act now

Detection Guidance

Detection should focus on behavior implied by the vulnerability: Outlook-associated activity that causes unexpected outbound connections, particularly connections that may trigger Windows authentication to external or untrusted systems. If NTLM disclosure or coercion is confirmed in an organization’s incident, investigators should determine whether Outlook initiated the connection and whether credentials were exposed outside approved boundaries.

No single log pattern can prove exploitation. A successful hunt requires correlation among Outlook process activity, outbound network connections, Windows authentication events, proxy or firewall telemetry, and endpoint alert data. Preserve evidence from systems that were unpatched before the applicable update, particularly internet-facing or externally reachable workstations.

Technical Notes

A practical starting point is to hunt for outbound SMB or authentication-related traffic from user workstations to destinations outside approved internal ranges. For example, a network detection rule can flag SMB connections leaving the corporate network:

alert tcp $HOME_NET any -> !$HOME_NET 445
(
  msg:"Possible external SMB connection from workstation";
  flow:to_server,established;
  sid:1000124194;
  rev:1;
)

This is a triage signature, not a CVE-specific exploit signature. Tune exclusions for approved VPN, backup, management, and cloud services, and investigate any alert involving an Outlook user endpoint.

On Windows, review Security event 4624 for NTLM logons, especially unexpected source or destination relationships and logon types associated with network access. A Microsoft Sentinel-style starting query is:

SecurityEvent
| where EventID == 4624
| where AuthenticationPackageName =~ "NTLM"
| where TimeGenerated > ago(14d)
| project TimeGenerated, Computer, Account, LogonType,
          AuthenticationPackageName, IpAddress, WorkstationName
| order by TimeGenerated desc

Also review Windows Filtering Platform events such as 5156 where enabled, proxy logs for unusual outbound requests from Outlook-related activity, and endpoint telemetry for OUTLOOK.EXE spawning or initiating unexpected network access. The exact event fields and process visibility depend on the organization’s audit and EDR configuration.

For possible credential exposure, correlate endpoint detections with domain controller events, VPN authentication, proxy authentication, and identity-provider alerts. Look for unusual NTLM authentication from user workstations, authentication to unfamiliar hosts, impossible travel after workstation activity, or account use shortly after a suspicious Outlook event.

Remediation Steps

Install Microsoft’s November 10, 2026 Office security updates and verify the resulting build on every affected endpoint. The minimum fixed builds identified in the available references are:

  • Office LTSC 2021: 16.0.14334.21048 or later
  • Office LTSC 2024: 16.0.17932.21140 or later
  • Microsoft 365 Apps for Enterprise: the channel-specific fixed security build published in Microsoft’s advisory

Microsoft 365 Apps deployments must be evaluated by servicing channel. A build that is current for one channel may not be the applicable fixed build for another. The supplied material does not provide a complete authoritative Microsoft 365 affected range or one universal fixed build, so administrators should use the Microsoft advisory and Office servicing documentation as the source of truth.

Technical Notes

For Click-to-Run installations managed through the Office Deployment Tool or an enterprise software distribution platform, use the organization’s approved update process. A direct administrative update command for a Click-to-Run installation is:

"%ProgramFiles%\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user

On 32-bit Office installed on 64-bit Windows, the executable may instead be located at:

"%ProgramFiles(x86)%\Common Files\Microsoft Shared\ClickToRun\OfficeC2RClient.exe" /update user

The command initiates the normal Click-to-Run update workflow; it does not guarantee that the endpoint has reached the applicable fixed build. Validate afterward using ClientVersionToReport, Microsoft Intune, Configuration Manager, or the organization’s software inventory system.

For volume-licensed LTSC deployments, deploy the applicable Office security update through the organization’s standard Office update mechanism, such as Configuration Manager, an enterprise software distribution platform, or a controlled Office Deployment Tool configuration. Do not assume ordinary Windows Update will deliver every Office update, particularly for volume-licensed or separately managed installations.

Where patching cannot be completed immediately, reduce exposure while treating the control as temporary:

  1. Restrict outbound SMB and other unnecessary Windows authentication traffic from user workstations to the internet.
  2. Review and limit NTLM usage where operationally feasible.
  3. Apply Microsoft’s documented mitigations if the advisory provides any.
  4. Increase monitoring for Outlook-triggered external connections and unexpected NTLM authentication.
  5. If an affected product cannot be mitigated, follow CISA guidance to discontinue its use where practical.

After remediation, verify the installed build, restart Office if required, confirm that update management reports compliance, and preserve pre-patch telemetry. If exploitation is suspected, isolate the endpoint according to incident-response procedures, rotate potentially exposed credentials, assess lateral movement, and investigate authentication logs before deleting evidence.

Choosing a tool? Pricing and head-to-head guides

Last verified: 2026-11-14

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.