Loading vulnerability…
CVE-2025-26630 is a use-after-free vulnerability in Microsoft Access that can lead to code execution. The flaw is triggered when Access processes a specially crafted malicious file, causing the application to reference memory after it has been freed. Available reporting characterizes the issue as a remote code execution vulnerability in delivery terms, but exploitation occurs locally in the context of the user who opens the malicious Access file. Microsoft assessed exploitation as less likely and indicated that the Preview Pane is not an attack 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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
High-severity remote code execution vulnerability in Microsoft Access.
A Microsoft Access use-after-free code execution vulnerability that requires a user to open a malicious file; publicly disclosed but not reported as exploited in the wild.
Remote code execution vulnerability in Microsoft Access.
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.