Security alerts · November 18, 2026

Microsoft Outlook flaw that skips safety warnings is being actively exploited

Microsoft Office Outlook has a flaw, CVE-2026-124194, that fails to warn users before a potentially unsafe action. Attackers are already exploiting it, as confirmed by the US agency CISA and the European EUVD database. Update Outlook following Microsoft’s advisory as soon as possible.

What happened

A vulnerability in the Microsoft Office Outlook email client, tracked as CVE-2026-124194, was disclosed on November 10, 2026. The flaw means Outlook does not warn the user before a potentially unsafe action. According to Microsoft’s description, an attacker can use it for spoofing, meaning something is made to look more trustworthy than it really is.

The flaw is already being actively exploited. The US Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of exploited vulnerabilities on the same day, November 10, 2026. The European Vulnerability Database (EUVD), run by ENISA, also records exploitation since November 10, 2026.

These sources do not say who is behind the attacks or exactly how they work. Microsoft rates the flaw at CVSS 6.5, which is medium severity. The fact that attackers are already using it matters more than the number itself.

Why it is dangerous

The flaw falls under CWE-356: the user interface does not warn about an unsafe action. Picture a receptionist who is supposed to verify every unknown visitor with a phone call, but in one particular situation just waves them through. Outlook should show a warning before a risky step, but here it does not. The user ends up doing something they believe is safe when it is not.

The CVSS vector published by Microsoft tells us the following:

  • The attack works over the network. The attacker does not need physical or local access to the computer.
  • The attacker does not need any login or account in your organization.
  • A user has to take some action. The record does not say exactly what action.
  • The impact on confidentiality is high: the attacker can obtain sensitive information. Microsoft does not specify what kind in the record.
  • The impact on integrity and availability is rated as none. This is not a direct takeover of a computer or server.

CVSS is a severity scale from 0 to 10. The 6.5 score was assigned by Microsoft itself using CVSS 3.1 and corresponds to medium severity. The CISA KEV (Known Exploited Vulnerabilities) catalog only lists flaws that CISA knows are being exploited in real attacks. CISA does not currently know whether this flaw is used in ransomware campaigns.

EPSS is a model that estimates the probability of exploitation within the next 30 days. As of November 18, 2026, it stands at 1.62%, higher than roughly 76.6% of all scored vulnerabilities. Since exploitation is already confirmed, EPSS is of secondary importance here.

Who is affected

This affects organizations that use the Microsoft Office Outlook email client. Typically that means staff desktops and laptops running Office or Microsoft 365, where people open emails from external senders every day.

The NVD and CISA records do not list the specific affected Outlook versions and editions. You will find the exact list in Microsoft’s MSRC advisory for CVE-2026-124194. These sources also do not say whether Outlook on the web, Outlook for Mac or the mobile apps are affected, so check the advisory.

The people likely to be most exposed are those who receive a lot of external mail: management, accounting, sales and HR.

How to check if you are affected

You can find the version directly in Outlook: File > Office Account > About Outlook (names may vary slightly between versions). It shows both the version and the build number.

On Click-to-Run installations (Microsoft 365), you can check the version from the command prompt. The command only reads the registry and changes nothing:

reg query "HKLM\SOFTWARE\Microsoft\Office\ClickToRun\Configuration" /v VersionToReport

A list of installed Office and Microsoft 365 products in PowerShell, also read-only:

Get-ItemProperty "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*", "HKLM:\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*" | Where-Object { $_.DisplayName -like "*Office*" -or $_.DisplayName -like "*Microsoft 365*" -or $_.DisplayName -like "*Outlook*" } | Select-Object DisplayName, DisplayVersion

Compare the build number with the fixed build for your edition in Microsoft’s advisory. If you manage many machines, your device management tool, such as Intune or Configuration Manager, can also report Office versions.

How to fix it

Neither the NVD nor the CISA record lists fixed versions. Microsoft publishes the fixed build numbers and current guidance in its MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-124194.

  • Open Microsoft’s advisory and find your Office or Outlook edition and the build that fixes the flaw.
  • For Microsoft 365 and other Click-to-Run installations, go to File > Office Account > Update Options > Update Now in Outlook, then restart Outlook.
  • For classic (MSI) installations, deploy the security update listed in the advisory via Windows Update, WSUS or your device management tool.
  • After updating, confirm the build number again using the steps in the previous section.

Order of priority: start with the machines of people who receive the most external email and have access to sensitive data, such as management, finance and HR. Then everyone else. Since the flaw is already being exploited, do not wait for your regular monthly patch cycle.

CISA requires US federal agencies to apply mitigations per the vendor’s instructions by November 24, 2026, or to stop using the product if mitigations are unavailable. This deadline is not binding for European companies, but it is a useful benchmark.

Check Microsoft’s advisory to see whether it also lists a workaround. Until the update is deployed, remind staff to be careful with unexpected emails, attachments and links, even when they look trustworthy.

What if you may already be compromised

Neither Microsoft nor CISA has published specific indicators of compromise in these records. It is therefore worth checking for general signs of email account abuse, especially for the period since November 10, 2026.

  • Unusual sign-ins in Microsoft 365 (Entra ID): unfamiliar countries, devices or times.
  • New inbox rules and automatic forwarding to external addresses.
  • New apps with mailbox access, changed passwords or changed multi-factor authentication methods.
  • Emails that staff reported as suspicious, and messages impersonating known senders.

If you find any of these, reset the affected account’s password, sign out all of its sessions and remove unknown rules. If you suspect sensitive data was leaked or you are unsure of the scope, bring in an incident response specialist. If personal data was exposed, remember the breach notification duty under GDPR.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.