CVE-2026-32189 is a Microsoft Office Excel vulnerability caused by a use-after-free condition (CWE-416). According to the provided content, successful exploitation occurs when an attacker delivers a malicious Office file to a target and convinces the user to open it in Excel. The flaw can then be triggered during local processing of the crafted file, resulting in code execution on the victim system. Microsoft classifies the issue as a remote code execution vulnerability because the attacker can initiate the attack remotely by sending the file, even though the actual code execution occurs locally on the user’s machine. Microsoft also states that the Preview Pane is not an attack vector for this issue.
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.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.