Loading vulnerability…
CVE-2026-55045 is a Critical vulnerability in Microsoft Office that is described as an out-of-bounds read and can lead to code execution. The issue is triggered when Microsoft Office processes a specially crafted document or other crafted Office content. Available reporting indicates the flaw affects Microsoft Office document handling and that exploitation occurs in the security context of the logged-on user. Although one advisory summary refers to a type confusion condition in Microsoft Office, the specific CVE is consistently identified elsewhere as an out-of-bounds read. Successful exploitation results in local code execution from attacker-supplied content, making it a practical phishing and document-based initial access vector.
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.
A critical Microsoft Office remote code execution vulnerability caused by an out-of-bounds read.
A critical remote code execution vulnerability in Microsoft Office, typically triggered by opening a specially crafted document.
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.