Loading vulnerability…
CVE-2025-34106 is a buffer overflow vulnerability in PDF Shaper versions 3.5 and 3.6. The issue is triggered when the PDFTools.exe component processes a maliciously crafted PDF file via the application's 'Convert PDF to Image' functionality. Successful exploitation can occur if an attacker convinces a user to open or convert the crafted PDF, causing memory corruption that can lead to arbitrary code execution in the security context of the current user. The vulnerability has been reported as verified on Windows XP, Windows 7, Windows 8, and Windows 10.
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.
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/shaper_pdf_bof.rb) that exploits a buffer overflow vulnerability (CVE-2025-34106) in PDF Shaper versions 3.5 and 3.6 on Windows platforms (XP, 7, 8, 10). The exploit works by generating a malicious PDF file (default name: msf.pdf) containing a specially crafted JPEG stream. When the target application processes this PDF using the 'Convert PDF to Image' feature, a buffer overflow is triggered in PDFTools.exe, allowing arbitrary code execution via a customizable Metasploit payload. The module is operational and allows the attacker to select payloads, but requires user interaction (the victim must open the malicious PDF in the vulnerable application). The code is written in Ruby and leverages Metasploit's FILEFORMAT, PDF, and SEH exploitation mixins. No network endpoints are involved; the attack vector is local file execution.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.