Loading vulnerability…
CVE-2025-47175 is a use-after-free vulnerability in Microsoft Office PowerPoint. The flaw arises from improper handling of object lifetime in PowerPoint, allowing memory to be reused after it has been freed. An attacker who can trigger the condition may be able to corrupt memory and execute arbitrary code in the context of the affected application. The available information identifies the issue as a local code execution vulnerability affecting PowerPoint and does not provide further detail on the specific vulnerable function or parsing component.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository provides a Proof-of-Concept (PoC) exploit for CVE-2025-47175, a Use-After-Free vulnerability in Microsoft PowerPoint (2019 and Office 365, pre-June 2025 patch). The main file, CVE2025-47175.py, is a Python script that generates a malicious PPTX file containing crafted XML designed to trigger the UAF condition when opened in a vulnerable PowerPoint installation. The exploit does not include shellcode or a full RCE payload, but demonstrates the ability to create a document that could be used as a delivery vector for further exploitation. The attack vector is local, requiring user interaction (opening the file). The repository also includes a README with usage instructions and a LICENSE file. No network endpoints or remote services are involved; all fingerprintable endpoints are file paths related to the generated PPTX structure.
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.