> ## Content Index
> Fetch the complete content index at: https://f4n6.co.uk/llms.txt
> Use this file to discover other available public pages before exploring further.

# Outlook spoofing CVE-2026-124194 actively exploited in wild
- URL: https://f4n6.co.uk/security-feed/outlook-spoofing-cve-2026-124194-actively-exploited-in-wild/
- Published: 2026-11-13T11:59:05.000Z
- Updated: 2026-11-13T11:59:05.000Z
- Author: Jeff Davies
- Tags: #security-feed, CVE-2026-124194, CVE-2026-125350

## 1\. Executive summary

Microsoft's November 2026 Patch Tuesday fixes more than 1,000 vulnerabilities, and one of them, CVE-2026-124194, a spoofing flaw in Microsoft Outlook, is confirmed by Microsoft as exploited in the wild. The flaw is rated 6.5 MEDIUM (CWE-356) and is listed in CISA KEV with an add date of 2026-11-10; a second CVE covered in the same patch cycle, CVE-2026-125350 in Google Chrome, is rated 8.8 HIGH (CWE-416) and is also in CISA KEV as of 2026-11-10\. Exploitation of CVE-2026-124194 requires a user to open a crafted message file, after which Outlook connects to an attacker-controlled location without the usual external-content warning and discloses the user's NTLMv2 hash, which can be relayed or cracked to impersonate the user. For EMEA financial services the exposure is concentrated in Microsoft 365 Apps for Enterprise and Office desktop estates, where a single opened file yields a reusable credential rather than code execution. The medium score understates operational impact: the output is an authentication credential valid against services that accept NTLM.

## 2\. Regulatory framing

| Article                                                                         | Trigger (the fact in this item)                                                                                                                                                                                                                 | Practical impact                                                                                                                                                                     |
| ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| DORA Art. 19: reporting of major ICT-related incidents to competent authorities | CVE-2026-124194 is confirmed exploited in the wild and discloses NTLMv2 hashes that can authenticate as the user; where that yields unauthorised access to production systems, it is an ICT-related incident to classify and, if major, report. | Clients must be able to evidence detection, classification and, where major, notification of incidents arising from this flaw; patch status alone does not discharge the obligation. |
| DORA Art. 28: ICT third-party risk, general principles                          | The affected component is Microsoft Office/Outlook, supplied as a third-party product, and the fix is delivered through the vendor's update channel.                                                                                            | Clients must track that the Office update is applied across the estate and record the dependency and its remediation state.                                                          |

No NIS2 or UK NIS article is engaged by the facts here beyond the general incident-handling duties already covered above.

## 3\. Technical analysis & attack chain

CVE-2026-124194 is a spoofing vulnerability in Microsoft Outlook, rated 6.5 MEDIUM with CWE-356 (product UI does not warn user of unsafe actions). Microsoft confirms it was exploited in the wild as a zero-day. The affected products named in Microsoft's advisory are Microsoft 365 Apps for Enterprise and editions of Microsoft Office. The flaw is patched through the affected Office products, not through the Windows update channel.

Confirmed exploitation chain, as described by TrendAI Zero Day Initiative's Dustin Childs and repeated by CrowdStrike and Malwarebytes:

1. The attacker sends a specially crafted message file to the target, delivered by email or another channel.
2. The attacker convinces the user to open the file. User interaction is required; the Preview Pane is not an attack vector for this CVE.
3. Outlook processes the file and connects to an attacker-controlled network location.
4. The usual external-content warning is not displayed, so the user receives no prompt that an outbound connection to an untrusted location is being made.
5. The connection discloses the user's NTLMv2 hash to the attacker-controlled location.
6. The attacker relays or cracks the captured hash offline to impersonate the user against other services that accept NTLM authentication.

The mechanism is a credential-disclosure primitive, not remote code execution. The value to an attacker is a reusable authentication artefact. CrowdStrike notes the Moderate rating reflects the user-interaction requirement, and that the real-world exposure is broader than the score suggests because the flaw requires only a file open, bypasses visible warnings, and yields reusable authentication material. The Register quotes Childs making the same point: "It's labeled spoofing, but the impact is bigger than the name suggests."

Microsoft has not stated when the attacks started, who is carrying them out, or what is done with the access after exploitation. No threat actor is named in any source for this CVE, and no MITRE ATT&CK profile is associated with it. Attribution is therefore unconfirmed.

The second KEV entry in this patch cycle, CVE-2026-125350, is a use-after-free (CWE-416) in Google Chrome's XML component, rated 8.8 HIGH. Google released Chrome version 157.0.8103.50 to fix it, alongside eight other security holes. The flaw allows a remote attacker to execute arbitrary code within Chrome's sandbox through a specially crafted HTML page, and Google confirmed an exploit exists in the wild. The Register reports this is the sixth Chrome zero-day of the year and that the bug is also patched in Chromium-based browsers such as Edge.

The wider patch cycle: Microsoft fixed between 1,093 and 1,095 vulnerabilities depending on the source (Tenable and Krebs report 1,093; The Register and Talos report 1,094 and 1,095 respectively), with 63 or 64 rated critical. The Register reports CVE-2026-124194 is the only one under active exploitation and none are listed as publicly known. Two zero-click critical flaws at 9.8 CVSS are also in the release: CVE-2026-116928, an out-of-bounds write in the Windows Search Component reachable through Exchange auto-indexing of an email attachment without the recipient opening it, and CVE-2026-119958, an out-of-bounds write in Windows LDAP reachable through crafted LDAP requests against domain controllers. Neither is reported as exploited. These are separate CVEs from the two KEV entries and carry no KEV status.

The Talos newsletter also carries file-reputation entries for five samples (SHA256 f4b1f888..., 7fc50b69..., ae59aedc..., f0f8ceed..., 985c3972...) with detection names including W32.F4B1F888F2-95.SBX.TG, Win.Tool.Kmsauto::1201 and W32.AE59AEDC4D-95.SBX.TG. The newsletter does not state which campaign, actor or CVE these samples belong to, and they are not tied to CVE-2026-124194 or CVE-2026-125350 in the source. They are reproduced in §5 as-is, with that caveat.

## 4\. Mitigation & containment

P1 within 24 hours

- Apply the Office update that fixes CVE-2026-124194 to all Microsoft 365 Apps for Enterprise and Microsoft Office installations. The fix ships through the Office update channel, not Windows Update; confirm the Office channel has picked it up on endpoints where Windows patching is automated. No specific KB number is named in public reporting.
- Update Chrome to version 157.0.8103.50 (or later) for CVE-2026-125350, and apply the equivalent update to Chromium-based browsers including Edge.
- Block outbound NTLM authentication from workstation and Office endpoint segments to the internet and to untrusted internal hosts at the perimeter and host firewall. This removes the disclosure path for the captured hash even on unpatched endpoints.
- Enforce SMB signing and LDAP signing/channel binding, and disable NTLM where the environment permits, to reduce the value of a captured NTLMv2 hash for relay.
- Hunt mail gateways and endpoint telemetry for message files delivered to Outlook users in the days before the patch, and for Outlook processes making outbound connections to unfamiliar external hosts.

P2 within 72 hours

- Patch Exchange Server and domain controllers for the zero-click criticals in the same release (CVE-2026-116928, CVE-2026-119958) and for the critical RCEs in externally facing or core services. The Register quotes Childs advising defenders to patch Exchange and Domain Controllers (LDAP/Kerberos) first, ring-fence exposed DNS and DHCP, and verify manual administrative fixes on cloud services.
- Deploy the Snort rules Talos published alongside its Patch Tuesday coverage to buy time on unpatched segments. The rule content is in the full Talos blog post, not in the newsletter text.
- Reset credentials and review authentication logs for any user who opened a suspicious message file, treating the NTLMv2 hash as compromised.

P3 within 7 days

- Review the remaining critical RCEs in the release against external exposure and prioritise those reachable from the internet or from email.
- Verify that Office update compliance is reported separately from Windows update compliance in the patch dashboard, since this CVE does not appear in the Windows channel.

## 5\. Indicators of compromise

No network indicators, command-and-control addresses or exploitation artefacts for CVE-2026-124194 or CVE-2026-125350 are given in public reporting. The file hashes below are from the Talos newsletter's file-reputation section; the newsletter does not attribute them to either CVE or to any named campaign, so treat them as single-sourced and unlinked to this exploitation until confirmed.

| type   | value                                                            | confidence            | source                          |
| ------ | ---------------------------------------------------------------- | --------------------- | ------------------------------- |
| sha256 | f4b1f888f29faa7fbec180f42bdc78596e8a8b908c0a6e6c419933703c81df85 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| md5    | 95a6a4b638cfdfbe3afc883d593a1f87                                 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| sha256 | 7fc50b69b56bfdfa9fc0a3e088ff13904587d6336a51e9edcc7919cba83d4e3f | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| md5    | cca616647db9370c88998ae25da6997f                                 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| sha256 | ae59aedc4d89d7b22db5dc65cd0b2ff68b20b74863d44f53fd346de739081694 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| md5    | 1fd9ccecac8794f39d826fdd8a62e6bc                                 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| sha256 | f0f8ceed9d5db100de257e6c8a4c85b08a30fd9591de754169adcfe0cf627bcb | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| md5    | 57ddcd4384fd595a12df5a6258e5af4d                                 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| sha256 | 985c3972712218c62d2418b41056dba5fe883ca5104d8ec12041f8611db344f9 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |
| md5    | 485055033bcddfde56325c0d2feea4f2                                 | low (unlinked to CVE) | Talos Threat Source, 2026-11-12 |

```iocs
sha256  f4b1f888f29faa7fbec180f42bdc78596e8a8b908c0a6e6c419933703c81df85
md5  95a6a4b638cfdfbe3afc883d593a1f87
sha256  7fc50b69b56bfdfa9fc0a3e088ff13904587d6336a51e9edcc7919cba83d4e3f
md5  cca616647db9370c88998ae25da6997f
sha256  ae59aedc4d89d7b22db5dc65cd0b2ff68b20b74863d44f53fd346de739081694
md5  1fd9ccecac8794f39d826fdd8a62e6bc
sha256  f0f8ceed9d5db100de257e6c8a4c85b08a30fd9591de754169adcfe0cf627bcb
md5  57ddcd4384fd595a12df5a6258e5af4d
sha256  985c3972712218c62d2418b41056dba5fe883ca5104d8ec12041f8611db344f9
md5  485055033bcddfde56325c0d2feea4f2

```

Behavioural indicators

| behaviour                                                                                                                                          | where to observe                                                         | confidence                                           |
| -------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ---------------------------------------------------- |
| Outlook process makes an outbound connection to an external host shortly after a user opens a message file, with no external-content warning shown | Endpoint network telemetry, proxy logs, Outlook client logs              | medium (described by ZDI, CrowdStrike, Malwarebytes) |
| NTLMv2 authentication attempts from a workstation to an external or unexpected host                                                                | Domain controller authentication logs, NTLM event logging, perimeter IDS | medium                                               |
| Message files delivered to Outlook users that trigger an outbound connection on open                                                               | Mail gateway logs, endpoint EDR file-open telemetry                      | medium                                               |

## 6\. Detection

The sources give no distinctive strings, filenames, registry keys or command lines for the CVE-2026-124194 exploitation itself. The only file artefacts are the five sample hashes in §5, which are not attributed to this CVE. A YARA rule built on those hashes would be a hash-match rule, not a string-based detection of the threat, and the newsletter gives no strings from inside the samples. On that basis no YARA rule is emitted for this advisory.

A Sigma rule for the behavioural pattern (Outlook making an outbound connection after a message file open) is possible, but the sources do not give the process names, ports or destination patterns needed to make it specific enough to avoid false positives across every Outlook deployment. Emitting one would be guesswork.

Insufficient indicators to author detection rules.

## CVE assessment

2 referenced CVEs — **2 actively exploited (CISA KEV)**

| CVE                                                                                | CVSS       | Exploited        | EPSS | Summary                                                                                                                          |
| ---------------------------------------------------------------------------------- | ---------- | ---------------- | ---- | -------------------------------------------------------------------------------------------------------------------------------- |
| [CVE-2026-125350](https://nvd.nist.gov/vuln/detail/CVE-2026-125350?ref=f4n6.co.uk) | 8.8 High   | ⚠ KEV 2026-11-10 | 1%   | Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sa… |
| [CVE-2026-124194](https://nvd.nist.gov/vuln/detail/CVE-2026-124194?ref=f4n6.co.uk) | 6.5 Medium | ⚠ KEV 2026-11-10 | 2%   | Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing… |

## 7\. Sources

- Cisco Talos, "Never be afraid to ask questions", Threat Source newsletter, 2026-11-12\. https://blog.talosintelligence.com/never-be-afraid-to-ask-questions/
- Krebs on Security, "Microsoft Fixes Nearly 1,100 Security Vulnerabilities", November 2026\. https://krebsonsecurity.com/2026/11/microsoft-fixes-nearly-1100-security-vulnerabilities/
- The Register, "November Patch Tuesday boasts over 1,000 bugs but only one zero-day so far", 2026-11-10\. https://www.theregister.com/security/2026/11/10/november-patch-tuesday-boasts-over-1000-bugs-but-only-one-zero-day-so-far/5308946
- The Register, "November Patch Tuesday boasts over 1,000 bugs, one already under attack", 2026-11-10\. https://www.theregister.com/security/2026/11/10/november-patch-tuesday-boasts-over-1000-bugs-one-already-under-attack/5308946
- CrowdStrike, "November 2026 Patch Tuesday: 1,252 CVEs Include One Zero-Day and 68 Critical Vulnerabilities", November 2026\. https://www.crowdstrike.com/en-us/blog/patch-tuesday-analysis-november-2026/
- Tenable Research, "Microsoft's November 2026 Patch Tuesday addresses 1093 CVEs (CVE-2026-124194)", November 2026\. https://www.tenable.com/blog/microsoft-november-2026-patch-tuesday-addresses-1093-cves-cve-2026-124194
- Malwarebytes Labs, "Microsoft Patch Tuesday fixes Outlook flaw already under attack", November 2026\. https://www.malwarebytes.com/blog/bugs/2026/11/microsoft-patch-tuesday-fixes-outlook-flaw-already-under-attack

## 8\. Adverse Trace position

Adverse Trace assesses CVE-2026-124194 as a medium-severity credential-disclosure flaw whose operational impact for financial services is higher than its 6.5 score implies, because a single opened message file yields an NTLMv2 hash that can authenticate as the user against services accepting NTLM; CISA KEV listing as of 2026-11-10 confirms exploitation. CVE-2026-125350 is rated 8.8 HIGH and is also in CISA KEV as of 2026-11-10; the Chrome fix is straightforward and should be applied in the same window. No actor is named for either CVE and attribution is unconfirmed. The file hashes in §5 are single-sourced from the Talos newsletter and unlinked to either CVE; verify before enforcing. We will track Microsoft's advisory for the affected and fixed Office build numbers, monitor for any actor attribution or post-exploitation reporting on CVE-2026-124194, and update this advisory when either appears. Clients running Microsoft 365 Apps for Enterprise should confirm the Office update channel has applied the fix this week and report back on NTLM authentication anomalies observed in the preceding 14 days.

---

[Read the original source →](https://blog.talosintelligence.com/never-be-afraid-to-ask-questions/?ref=f4n6.co.uk)

*Published via PulseTrace — Adverse Trace threat intelligence.*