Skip to main content
Mallory
High

Type Confusion RCE in Microsoft Office Outlook/Word Preview Rendering

IdentifiersCVE-2026-47635CWE-122· Heap-based Buffer Overflow

CVE-2026-47635 is a Critical remote code execution vulnerability in Microsoft Office caused by access of a resource using an incompatible type (type confusion). The available reporting indicates the flaw is in the Office document parsing/rendering pipeline used by Microsoft Word functionality and exposed through Outlook Classic, which uses Word as its rendering engine, including for the Preview Pane. A specially crafted email body, rendered message content, or malicious document/attachment can cause the Word engine to interpret attacker-controlled data as a valid object or pointer, leading to controlled memory corruption and ultimately arbitrary code execution in the context of the logged-in user. Although Microsoft’s CVSS vector lists a local attack vector, the supporting content indicates exploitation can be initiated remotely by delivering crafted content over email and triggering the vulnerable rendering path when Office processes it.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation results in arbitrary code execution on the target system with the privileges of the victim user. Because the flaw affects Outlook Classic’s Word-based rendering path, exploitation may occur during message rendering, including via the Preview Pane, potentially without the user explicitly opening an attachment. This can enable compromise of confidentiality, integrity, and availability on the affected host, and may serve as an initial access vector that can be chained with privilege escalation, persistence, or lateral movement techniques.

Mitigation

If you can’t patch tonight, do this now.

If patching cannot be applied immediately, reduce exposure by disabling or limiting the Outlook Classic Preview Pane for untrusted mailboxes, enforcing Protected View for files originating from the internet, and applying Attack Surface Reduction rules that restrict Office applications from spawning child processes. Defenders should also monitor for unusual Office rendering crashes, memory-access violations, suspicious child processes from Word or Outlook, and anomalous behavior tied to specific messages or attachments. These measures reduce exploitability but do not fully remediate the underlying engine flaw.

Remediation

Patch, then assume compromise.

Apply the Microsoft June 2026 security updates for all affected Microsoft Office, Word, and Outlook Classic product lines and builds that use the vulnerable rendering components. Administrators should ensure each installed Office SKU receives its corresponding security package, including LTSC and Microsoft 365 channels where applicable. Priority should be given to systems that process untrusted email content in Outlook Classic.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationOfficeapplication
Microsoft CorporationOffice 2024application

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.