Loading vulnerability…
CVE-2026-45463 is a critical Microsoft Office vulnerability caused by an integer underflow, described in associated advisories as leading to a buffer overflow condition. Successful exploitation allows an unauthorized attacker to execute code locally in the context of the affected Microsoft Office application. Available reporting also indicates the Preview Pane is a viable attack vector, meaning exploitation may be triggered during content rendering rather than only through full document interaction. The flaw affects Microsoft Office and has been grouped among the high-priority Office vulnerabilities addressed in Microsoft’s June 2026 security updates.
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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Critical Microsoft Office remote code execution vulnerability with a Preview Pane attack vector, highlighted as a priority patch.
A critical local code execution vulnerability in Microsoft Office caused by a use-after-free flaw.
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.