IRONSMITHINTEL
CRITICALCVSS9.8
|CVE-2025-21298|Auth: none — outlook auto-preview is sufficient|Reboot: required|Est. 30–60 minutes including reboot|Manual only

Windows OLE Use-After-Free — Outlook Preview-Pane RCE With No User Interaction (CVE-2025-21298)

A use-after-free in Windows OLE allows remote code execution when Outlook previews a specially crafted email — no clicks required. Apply the January 2025 cumulative update, or configure Outlook to render messages as plain text until patched.

Published Jan 14, 2025 · Updated May 16, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

An attacker who can email the victim — internal user, external phisher, or any inbox-spam path — can execute code in the user's context the moment Outlook previews the message. On a server where Outlook is installed (e.g. a jump host, RDS session host with Office, or admin workstation accessed via remote console), this is a path to interactive code execution with the privileges of whatever account is signed in. On RDS deployments this typically yields a foothold inside the broader environment.

How the attack works

A use-after-free vulnerability in Windows OLE is triggered when Outlook automatically parses a crafted RTF-encoded email in the reading pane. The flaw lets a remote attacker corrupt heap memory and ultimately execute arbitrary code in the user's context. Affected: Windows 10/11 and Windows Server 2008 SP2 through Windows Server 2025, prior to the January 2025 Patch Tuesday. Microsoft rates exploitation "More Likely" because the trigger is automatic email preview — the attacker only needs the victim's mailbox to receive the message.

Am I affected?Quick check

Probably yes if any of these apply:

RDS Session Hosts with Office Installed
Admin Jump Hosts
Any Windows Server with Outlook installed
End-user workstations with Outlook
Running Windows Server 2008 SP2 through Windows Server 2025, prior to the January 2025 cumulative update

Affected OS versions

Windows Server 2008 SP2Windows Server 2008 R2 SP1Windows Server 2012Windows Server 2012 R2Windows Server 2016Windows Server 2019Windows Server 2022Windows Server 2022 23H2Windows Server 2025
Fixed inJanuary 2025 Patch Tuesday cumulative update (see manual_steps for per-OS KB lookup)
Real-world incidentsWhat we've seen

CVE-2025-21298 was reported by an anonymous researcher and patched in the January 2025 Patch Tuesday rollup. Microsoft's only pre-patch workaround was configuring Outlook to display messages as plain text — a setting most enterprises cannot deploy without serious user complaints. Multiple security firms published technical analyses within days; a working PoC that triggers controlled heap corruption was demonstrated publicly. The wormable, no-click delivery path makes this comparable to historical Outlook/MSHTML preview-pane bugs.

How to patch

Manual remediation steps

30–60 minutes including reboot

Workaround until patched — Outlook plain-text reading

# Force Outlook to read messages as plain text (per-user setting).
# Substitute the correct Office version in the registry path (16.0 for current).
New-Item -Path "HKCU:\Software\Microsoft\Office\16.0\Outlook\Options\Mail" -Force
Set-ItemProperty -Path "HKCU:\Software\Microsoft\Office\16.0\Outlook\Options\Mail" `
  -Name "ReadAsPlain" -Value 1 -Type DWord
# Users must restart Outlook for the setting to take effect.

Group Policy deployment of the workaround

# Office Group Policy Templates → Microsoft Outlook → Outlook Options →
# Preferences → E-mail Options → "Read all standard mail in plain text" = Enabled

Apply the January 2025 cumulative update

1
Open Microsoft Update Catalog: https://catalog.update.microsoft.com
2
Search for CVE-2025-21298 to find the current superseding cumulative for your OS
3
Approve via WSUS / SCCM, or download the MSU and run as Administrator
4
Restart the server / workstation

Verify

# Confirm the OLE binary is patched:
(Get-Item C:\Windows\System32\ole32.dll).VersionInfo.FileVersion
# After verification, remove the plain-text workaround if applied.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.