Home › Vulnerabilities

Microsoft Office: Exploited Flaw CVE-2026-124194

Published November 10, 2026 · Last updated November 10, 2026

Microsoft Office CVE KEV Patch

What happened: On November 10, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added CVE-2026-124194, a flaw in Microsoft Office, to its Known Exploited Vulnerabilities (KEV) catalog. The catalog lists flaws CISA has evidence attackers are using. CISA calls this one the "Microsoft Office Outlook Missing User Interaction for Potentially Unsafe Action Vulnerability."

CISA's summary: "Microsoft Office Outlook contains a missing user interaction for potentially unsafe action vulnerability that allows an unauthorized attacker to perform spoofing over a network."

CVE-2026-124194 is a spoofing vulnerability in Microsoft Outlook that Microsoft says attackers have already exploited. Microsoft fixed it in its November 10, 2026 security release and marked it "Exploitation Detected." The same day, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added it to its Known Exploited Vulnerabilities catalog.

The flaw does not let an attacker take over a computer directly. Instead, it can leak the password hash Windows uses to sign a person in to network services. An attacker who captures that hash can use it to pose as the victim. That is why a bug Microsoft rates as Moderate still deserves prompt attention.

How the attack works

Microsoft classifies the weakness as CWE-356, "Product UI does not Warn User of Unsafe Actions." Normally, when a message or document tries to load content from an outside server, Outlook shows a warning first. This bug skips that warning.

Microsoft's FAQ for the CVE describes the attack in plain terms. An unauthenticated attacker "could send a specially crafted message file and convince a user to open it in an affected version of Microsoft Outlook." Opening the file "could cause Outlook to connect to an attacker-controlled network location without displaying the usual external-content warning, potentially disclosing authentication information that could be used to impersonate the user."

Microsoft also says what leaks: the bug "discloses a user's NTLMv2 hash to the attacker who could use this to authenticate as the user." NTLM is an older Windows sign-in protocol that is still widely enabled inside companies. A stolen NTLMv2 hash can be cracked offline to recover a weak password, or relayed to another service that accepts NTLM.

What the attacker needs

  • A victim who opens a file. Microsoft says "user interaction is required" and that the attacker "must send a user a malicious Office file and convince them to open it." Phishing email is the obvious delivery method.
  • No preview-only path. Microsoft states that "the Preview Pane is not an attack vector," so just selecting a message in the reading pane is not enough.
  • A network path out. Microsoft notes that exploitation "requires network connectivity," because Outlook has to reach the attacker's server for the hash to leave the machine.
  • No account on the target. The attacker does not need credentials or any foothold on the victim's network to send the lure.

Affected products and fixed builds

Microsoft's Security Update Guide lists these products as affected, each with a fix:

  • Microsoft Office LTSC 2021 (32-bit and 64-bit): fixed in build 16.0.14334.21048.
  • Microsoft Office LTSC 2024 (32-bit and 64-bit): fixed in build 16.0.17932.21140.
  • Microsoft 365 Apps for Enterprise (32-bit and 64-bit): Microsoft points to its Office security release notes at https://aka.ms/OfficeSecurityReleases for the patched build on each update channel.

Microsoft marks "Customer Action Required: Yes" for this CVE. Office versions not on that list are not described as affected in the advisory, and this article does not guess about them.

Severity and who scored it

Microsoft, which is also the CVE Numbering Authority for its own products, scored the flaw CVSS 3.1 6.5 (Medium), vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. Its own severity rating is Moderate. Microsoft's temporal metrics say exploit code maturity is still "Unproven" (E:U) and an official fix exists (RL:O), even though its exploitability assessment says exploitation has been detected.

The score stays in the medium range because the bug only exposes information and needs the user to act. It does not change data or crash anything on its own. The real-world risk is higher than the number suggests, because stolen NTLM credentials are a common first step toward wider break-ins. As of the afternoon of November 10, 2026, NVD had not added its own assessment, and no CISA ADP score appeared in the CVE record.

Microsoft credits Benoît Sevens and a researcher listed as "nono" with reporting the issue.

Exploitation status

Microsoft's advisory lists the flaw as "Publicly Disclosed: No; Exploited: Yes." CISA's catalog entry, added November 10, 2026, gives U.S. federal civilian agencies a deadline of November 24, 2026 to apply the fix. CISA lists ransomware use as "Unknown." Neither Microsoft nor CISA has published details about who used the flaw or against whom.

What to do

  • Office and IT administrators: install the November 2026 Office security updates now. For Office LTSC 2021, confirm Outlook reports build 16.0.14334.21048 or later. For Office LTSC 2024, confirm 16.0.17932.21140 or later. For Microsoft 365 Apps, check the Office security release notes for the fixed build on your update channel, then confirm devices have received it. Click-to-Run installs usually update automatically, but devices that were offline or paused may lag behind.
  • Home and small-business users: update Office yourself. In Outlook, open File, then Office Account, then Update Options, and choose Update Now. Restart Outlook when it finishes.
  • Security teams: limit NTLM leaks while patches roll out. Blocking outbound SMB (TCP port 445) at the network edge stops Windows from sending sign-in hashes to outside servers over that protocol. Microsoft's Protected Users group and policies that restrict outgoing NTLM traffic reduce the value of any hash that does leak. Microsoft does not list these as official workarounds for this CVE, so treat them as general hardening, not a replacement for the update.
  • Everyone: be careful with unexpected attachments. The attack needs a person to open a file. Be suspicious of attachments you were not expecting, even ones that look like ordinary Office documents or saved messages.
  • Incident responders: watch for signs of misuse. Look for Outlook making connections to unfamiliar external hosts and for unusual NTLM sign-ins from accounts whose users recently opened unexpected files. If you suspect a hash was stolen, reset that user's password.

Sources: Microsoft Security Update Guide entry for CVE-2026-124194; CISA Known Exploited Vulnerabilities catalog; the CVE record published by Microsoft.

What the National Vulnerability Database says

NVD first published CVE-2026-124194 on November 10, 2026. Its description, from the record's source ([email removed]), reads: "Product ui does not warn user of unsafe actions in Microsoft Office Outlook allows an unauthorized attacker to perform spoofing over a network."

How serious is CVE-2026-124194?

The CVSS 3.1 base score is 6.5 out of 10 (Medium), scored by microsoft.com. In plain terms: an attacker can reach the Office weakness over a network, including the internet; the attacker does not need an account; a user has to take an action, such as opening a file or link. The listed impact on Office data secrecy is high, on data integrity none, and on availability none. The full vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N.

Which Office versions are affected?

The CVE record lists these affected ranges:

  • 16.0.1 up to, but not including, https://aka.ms/OfficeSecurityReleases
  • 16.0.1 up to, but not including, 16.0.14334.21048
  • 16.0.0 up to, but not including, 16.0.17932.21140

If your Office version falls in one of these ranges, check Microsoft's advisory for the fixed release that applies to you.

What kind of weakness is it?

CISA and NVD map CVE-2026-124194 to the following weakness type in MITRE's Common Weakness Enumeration (CWE):

  • CWE-356: Missing User Interaction for Potentially Unsafe Action. MITRE's definition: "The product encounters a situation in which some of its behavior is security-critical and should be authorized by a human before progressing, but it does not properly consult with the human user or its proxy (such as UI approval dialogues or pre-set policies) to determine whether it is allowed to perform the potentially dangerous behavior. (Roles: Acronym)"

CISA required action for CVE-2026-124194

CISA's required action for this KEV catalog entry, quoted from the catalog record, is: "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines."

Timeline for CVE-2026-124194

  • November 10, 2026: CISA adds CVE-2026-124194 to the KEV catalog.
  • November 10, 2026: NVD publishes CVE-2026-124194.
  • November 10, 2026: latest change to the NVD record (status: Awaiting Analysis).
  • November 24, 2026: due date for U.S. federal civilian agencies to act on CVE-2026-124194.

Advisories and technical references

The NVD record for CVE-2026-124194 links to these references; tags in brackets are NVD's labels:

What to do

  • Run Microsoft Office? Follow Microsoft's own advisory (linked under Sources) and apply the fix or mitigation it lists. CISA's required action for this entry is to apply the vendor's mitigations, or stop using the product if no mitigation is available.
  • Federal civilian agencies must act by November 24, 2026, CISA's due date for this entry. Other organizations can use that date as a deadline for Office too.
  • Ransomware use: CISA lists known ransomware campaign use for CVE-2026-124194 as "Unknown".
  • Don't run Office yourself? You don't need to install anything on your phone or home computer for this. If a call, text, or pop-up says your device is infected by "CVE-2026-124194" and asks for payment or remote access, that is a scam pattern, not a Microsoft alert.

CVE-2026-124194 record details from CISA and NVD

  • CISA forensic triage flag for CVE-2026-124194: No
  • Attack complexity for CVE-2026-124194: low
  • CVE-2026-124194 CVSS scope: unchanged
  • NVD sub-scores for CVE-2026-124194: exploitability 2.8, impact 3.6.
  • Who mapped the weakness type: the address listed on microsoft.com (Primary)
  • References in the NVD record: 1.

Sources

General education only, not security advice. Facts checked against the sources above on the date shown.