CVE-2026-124194 vs Outlook Critical RCEs: Patch This First
Verdict: patch the Moderate bug before the Critical ones.
Microsoft disclosed the Outlook zero-day CVE-2026-124194 in its November 2026 Patch Tuesday release on November 10, 2026. It carries a CVSS 3.1 score of only 6.5 in the CVE record, yet it was exploited before a fix existed and it discloses a user's NTLMv2 hash to the attacker.
CISA added it to its Known Exploited Vulnerabilities (KEV) catalog the same day, with a federal patch deadline of November 24, 2026. The three Critical Outlook remote code execution (RCE) flaws in the same release have no confirmed exploitation, so they come second.
TL;DR
CVE-2026-124194is an Outlook spoofing flaw (CWE-356) rated 6.5 Medium, and the only bug in the November 2026 release confirmed as exploited in the wild, according to BleepingComputer.- The victim has to open a crafted message file. Microsoft says it cannot be triggered through the Preview Pane.
- A successful attempt can make Outlook connect to an attacker-controlled location without the usual external-content warning, exposing the user's NTLMv2 hash.
- CISA's KEV deadline for US federal agencies is November 24, 2026.
- Microsoft has published no details of observed attacks: no attribution, no victim count, no named campaign.
- Indian organisations should note the CERT-In six-hour incident reporting clock if abuse is noticed.
What is CVE-2026-124194 and why does a 6.5 score matter?
The CNA record, published by Microsoft, describes the flaw as a case where the product's user interface does not warn the user of unsafe actions, allowing an unauthorised attacker to perform spoofing over a network.
The vector string is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N. In plain terms: network reachable, low complexity, no privileges, user interaction required, high confidentiality impact, no integrity or availability impact. The NVD mirror carries the same data.
The score is middling because the bug does not run code. The harm is credential exposure, and that is exactly what makes it useful to an attacker who wants to move into a network quietly.
The score measures worst-case technical impact. It says nothing about whether anyone is using the bug today.
How does the Outlook NTLMv2 hash disclosure work?
Microsoft's advisory, as quoted by SecurityWeek, says an unauthenticated attacker could send a specially crafted message file and convince a user to open it in an affected version of Outlook. Opening it could cause Outlook to connect to an attacker-controlled network location without the usual external-content warning, potentially disclosing authentication information that could be used to impersonate the user.
Microsoft's MSRC advisory states that the flaw discloses the user's NTLMv2 hash. A captured NTLMv2 hash can be relayed to, or cracked offline against, services that still accept NTLM authentication.
That is why the missing warning matters more than the score suggests. Email is the natural delivery channel, so any organisation whose staff open message files is within reach. No exploit detail is given here and none is needed to defend against it.
Which Outlook versions are affected?
Per the CNA record, the affected products are Microsoft 365 Apps for Enterprise (builds before the security release), Office LTSC 2021 before 16.0.14334.21048, and Office LTSC 2024 before 16.0.17932.21140, on 32-bit and x64 Windows.
Microsoft 365 Apps on Click-to-Run update themselves unless updates are paused, so check for paused update channels first. The fixed builds are listed in the MSRC advisory.
Is CVE-2026-124194 more urgent than the Critical Outlook RCEs?
For the next two weeks, yes. The same release includes Critical Outlook RCEs: CVE-2026-110043, CVE-2026-110068 and CVE-2026-111309. CrowdStrike notes that preview-pane RCEs are a recurring attack-surface pattern. If a working exploit for one of them appears, the blast radius is larger, because email delivery requires less user cooperation.
- Severity rating: Moderate, CVSS 6.5 vs Critical
- Exploited in the wild: Yes, confirmed vs Not known at time of writing
- Impact: NTLMv2 hash disclosure vs Code execution
- User action: Must open a crafted file vs Varies by CVE
- Preview Pane trigger: No, per Microsoft vs See each advisory
- Patch priority: First vs Same maintenance window, immediately after
The practical rule is to rank by exploitation evidence, then by score. In a release that Tenable counts at 1,093 CVEs with 63 rated Critical, the one exploited bug is the one rated Moderate.
Counts differ by vendor because of how Edge and Chromium fixes are tallied: SecurityWeek reports 1,094, BleepingComputer reports 1,235 including 142 for Edge, and CrowdStrike reports 1,252 including 68 Critical.
What is the CISA deadline for CVE-2026-124194?
CISA's alert of November 10, 2026 added six exploited CVEs, including this one and Chromium CVE-2026-125350. The KEV entry calls it "Missing User Interaction for Potentially Unsafe Action" and sets a due date of November 24, 2026 under BOD 26-04, with the action "apply mitigations in accordance with vendor instructions".
Ransomware use is listed as unknown, and forensic triage is not required under the directive. The KEV catalog is the reference for the entry. Barracuda flaws were added in the same batch, which we covered in our Barracuda ESG KEV deadline piece.
What should defenders do now?
- Patch Outlook and Office builds: Microsoft 365 Apps: confirm the security-release build in the MSRC advisory. LTSC 2021:
16.0.14334.21048or later. LTSC 2024:16.0.17932.21140or later. - Meet the CISA KEV deadline: US federal agencies: November 24, 2026 under BOD 26-04.
- Hunt for unexpected outbound connections: Look for Outlook processes making unexpected outbound network connections after a user opened a suspicious file (CrowdStrike guidance).
- Reduce NTLM exposure: Review where NTLMv2 authentication is still accepted, since a captured hash is only useful against services that take it.
- Report abuse in India: If abuse is noticed, report to CERT-In within 6 hours.
If you find evidence of hash capture, treat the account as compromised and rotate its credentials. Our guide to password manager setups covers rotation habits, and the patch-first playbook for WordPress shows the same triage logic on a different product. For the pace at which exploitation follows a fix, see the OpenSSH case.
What does this mean for organisations in India?
Microsoft's advisory gives no details of observed attacks, so detection falls to the defender. Under the CERT-In directions issued under section 70B(6) of the IT Act, service providers, intermediaries, data centres and bodies corporate serving India must report cyber incidents, including spoofing, identity theft, phishing and data leaks, within six hours of noticing them.
For an Indian enterprise, the operational lesson is that a silently exploited client-side bug starts a six-hour reporting clock the moment a hash capture is noticed. Agree who files the report before an incident, not during one.
Who found it, and who is attacking?
Microsoft's advisory credits two researchers, and the acknowledgment for one notes the use of Anthropic's Claude AI model, as SecurityWeek reports. The advisory says nothing about who exploited the flaw, how many victims there are, or whether a campaign is under way.
Any article that claims otherwise is guessing. Further background on how we handle such claims is in our editorial policy.
FAQ
Q: What is CVE-2026-124194?
A: It is a Microsoft Outlook spoofing vulnerability, rated CVSS 6.5, that can disclose a user's NTLMv2 hash when they open a crafted message file. It was exploited as a zero-day before the November 10, 2026 patch.
Q: Can CVE-2026-124194 be triggered through the Preview Pane?
A: No. Microsoft states that the user must open the malicious file, so previewing alone does not trigger it.
Q: When is the CISA deadline for CVE-2026-124194?
A: November 24, 2026, for US federal civilian agencies under BOD 26-04. Other organisations are not bound by it but should treat it as a practical target.
Q: Which Office builds contain the fix?
A: Office LTSC 2021 needs 16.0.14334.21048 or later and LTSC 2024 needs 16.0.17932.21140 or later. For Microsoft 365 Apps, check the fixed builds listed in the MSRC advisory.
Q: Is the exploitation linked to ransomware or a named group?
A: CISA lists ransomware use as unknown, and Microsoft has attributed the attacks to no one. No victim numbers have been disclosed.
Q: Do Indian organisations have to report it?
A: Under the CERT-In directions, a noticed incident such as spoofing or a data leak must be reported within six hours. The vulnerability itself is not reportable; an observed abuse of it is.
Comments
No comments yet. Start the discussion.