Microsoft has disclosed CVE‑2026‑42508, a remote code execution flaw in Outlook for Windows that scores 9.8 CVSS. The vulnerability is actively exploited. Patch Outlook 2021/2019/2016 and all supported Office 365 versions now. Disable external content rendering as a temporary mitigation.
Impact Overview
A remote code execution (RCE) vulnerability has been found in Microsoft Outlook for Windows. The flaw, tracked as CVE‑2026‑42508, allows an attacker to execute arbitrary code on a victim’s machine simply by sending a specially crafted email. The CVSS v3.1 base score is 9.8 (Critical). Microsoft’s threat intel confirms that the vulnerability is already being leveraged in the wild.
Affected Products
| Product | Versions Affected |
|---|---|
| Microsoft Outlook (stand‑alone) | 2021, 2019, 2016, 2013 |
| Outlook component of Microsoft 365 (formerly Office 365) | Current channel, Semi‑Annual Enterprise Channel |
| Outlook for Windows in Microsoft 365 Apps for enterprise | All supported builds |
The vulnerability also impacts any third‑party mail clients that embed the Outlook rendering engine, though Microsoft has not published a list of such products.
Technical Details
Outlook parses HTML and RTF content using the Microsoft Word rendering engine. CVE‑2026‑42508 arises from a use‑after‑free bug in the handling of OLE object references when processing an email that contains a crafted OLEObject tag with a malicious payload. The steps are:
- The attacker sends an email containing a malformed OLE object.
- Outlook’s parser allocates a buffer for the object, then frees it prematurely during a subsequent validation pass.
- The attacker’s payload re‑uses the freed memory, allowing execution of shellcode under the context of the logged‑in user.
- If the user has administrative rights, the attacker can gain full system compromise.
The flaw bypasses existing sandbox protections because the code runs in the Outlook process, which is granted the same privileges as the user session.
Exploit Timeline
- 2026‑03‑15: Initial report to Microsoft via the MSRC Vulnerability Disclosure Program.
- 2026‑04‑02: Private advisory issued to partners.
- 2026‑04‑12: First known exploitation observed in targeted phishing campaigns against financial institutions.
- 2026‑04‑20: Public advisory and patches released.
Mitigation Steps
- Apply the Microsoft Security Update – Download and install the patch from the Microsoft Update Catalog for your specific Outlook version. The update is labeled KB5078901.
- Temporarily disable external content – In Outlook, go to File → Options → Trust Center → Trust Center Settings → Automatic Download and check “Don’t download pictures or other content automatically in HTML e‑mail”. This blocks the malicious OLE object from loading.
- Enforce least‑privilege – Ensure users run with standard accounts, not local administrators. Use Microsoft Endpoint Manager to enforce this policy.
- Deploy Email Filtering – Update Exchange Online Protection (EOP) or on‑premises mail gateways to block messages containing the
OLEObjecttag with suspicious payloads. Microsoft provides a detection rule in the Threat Protection documentation. - Monitor for Indicators of Compromise (IoCs) – Look for processes named
outlook.exespawningpowershell.exewith encoded commands, or anomalous network connections to known C2 domains listed in the advisory.
Verification
After patching, verify the Outlook version number:
- Outlook 2021: 16.0.15806.20244 or later
- Outlook 2019: 16.0.10396.20017 or later
- Outlook 2016: 16.0.10396.20017 or later
Run
winveror check File → Office Account → About Outlook.
References
- Official Microsoft Security Advisory: https://msrc.microsoft.com/update-guide/en-us/vulnerability/CVE-2026-42508
- CVE Details: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2026-42508
- Patch download: https://www.catalog.update.microsoft.com/Search.aspx?q=KB5078901
- Guidance on disabling external content: https://learn.microsoft.com/en-us/outlook/trust-center/automatic-download
Take action now. The window for exploitation is open. Apply the patch and enforce the temporary mitigation without delay.
Comments
Please log in or register to join the discussion