CVE-2025-24075 is a stack-based buffer overflow vulnerability in Microsoft Office Excel. The flaw allows an unauthorized attacker to execute code in the context of the affected user. Available reporting identifies the issue as affecting Excel and classifies it as a code execution vulnerability with a CVSS score of 7.8. Although one source string describes the issue as allowing code execution locally, broader context around the Excel March 2025 vulnerabilities indicates exploitation may occur through a specially crafted Excel file delivered to a target and opened in the vulnerable application. Specific details about the vulnerable function, parsing routine, or memory-handling path are not currently available.
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 Excel.
A Microsoft Excel remote code execution vulnerability listed in the summary table.
Unknown (listed without product/description in provided content).
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.