0 Comments

If you run Outlook on Windows in Microsoft 365 Apps or Office LTSC, this is a stop-and-update alert. Microsoft confirmed that the only vulnerability it flagged as actively exploited in this month’s Patch Tuesday is a spoofing flaw in Outlook — CVE-2026-124194 — and CISA has already added it to its Known Exploited Vulnerabilities catalog. The catch: it doesn’t take a clever macro, a malicious link, or a misbehaving add-in. All it needs is for a victim to open one specially crafted message file. That’s it.

What the vulnerability is. Tracked as CVE-2026-124194, this is a spoofing weakness rooted in how Outlook’s user interface fails to warn you before performing a potentially unsafe action (CWE-356). An unauthenticated attacker sends a crafted message file — typically dropped onto the target’s machine via email attachment, a download, or a shared drive — and talks the user into opening it. Once opened, Outlook is forced to connect back to an attacker-controlled network location, and here’s the nasty part: it does so without displaying the usual external-content warning you’d expect to see.

That silent outbound connection hands the attacker your NTLMv2 authentication hash. From there the threat actor can either crack the hash offline or use it in a relay / “pass-the-hash” style attack to authenticate as you against other services that accept NTLM — email, VPN, file servers, domain-joined resources. The first malicious message file you open can effectively hand over credentials that impersonate you across the network.

Key facts to know:

• CVSS 3.1 score: 6.5, severity Moderate (network attack vector, low complexity, no privileges required, but requires user interaction).
• Exploitation status: Confirmed exploited in the wild as a zero-day; added to the CISA KEV catalog on November 10, 2026, with a federal patch deadline of November 24.
• Good news: The Outlook Preview Pane is NOT an attack vector for this CVE. Simply previewing the message in the reading pane won’t trigger it.
• Bad news: Microsoft ships no workaround and no documented mitigation for this flaw — the Office update is the only fix.
• Discovered by: researchers “nono” and Benoît Sevens.

How the attack works. The technique is a well-known one to defensive teams — forced authentication (MITRE ATT&CK T1187). Rather than directly “hacking” you out of nothing, the attacker weaponizes an application’s habit of quietly reaching out to network resources and capturing what the app sends along the way. Outlook normally warns before loading external content like images or remote objects. This bug disables that warning for certain crafted message files, turning a routine “open the attachment” into an outbound connection that leaks your credentials without any visible sign. Because the compromise requires user interaction and network connectivity, email-gateway scrubbing alone won’t fully protect you — a user has to actually open the file.

What’s affected.

• Microsoft 365 Apps for Enterprise (32- and 64-bit) — fix depends on your update channel, see aka.ms/OfficeSecurityReleases.
• Office LTSC 2021 — fixed in 16.0.14334.21048 or later.
• Office LTSC 2024 — fixed in 16.0.17932.21140 or later.

What you should do right now.

Patch first, everything else second. Deploy the November 2026 Office/Outlook update on every Windows endpoint immediately. CISA’s binding federal deadline is November 24 — enterprise and home users should not wait that long. This is the only documented remediation, so treat it as mandatory.

Check your actually-installed version. For LTSC machines, confirm Outlook is at or above the fixed builds above. For Microsoft 365 Apps, verify your channel’s monthly update is installed.

Harden your network now. Since open-source tools and one-liners can force outbound connections and scoop up hashes, disable NTLM where you can, and restrict outbound SMB/UNC traffic on workstations so an exploited Outlook can’t reach attacker infrastructure in the first place.

Segment and monitor. Widen detection for anomalous outbound SMB connections and unusual authentication from workstations, and re-check logs for any already-collected hashes being replayed.

Train the “don’t open it” reflex. Preview Pane is safe, so users can safely inspect genuine-looking messages. The danger is clicking Open on the attachment — coach people to double-check senders of any .msg/attached file types before opening, especially on machines with elevated privileges.

Bottom line. One opened message file, one silent outbound connection, and your NTLMv2 hash is in the attacker’s hands — no exploit-kit, no macro, no click on a malicious URL required. Microsoft has confirmed it’s being actively exploited, so this isn’t a theoretical patch-Tuesday footnote. Get the November Office update on every Windows box before the November 24 KEV deadline.

Patch now.

Leave a Reply