Most people treat PDF files as harmless containers for documents — invoices, contracts, resumes. The format has earned that reputation precisely because it's so ubiquitous and boring. But beneath that benign exterior lies a feature that attackers have been quietly abusing for years: the PDF Launch action. Recent vulnerability disclosures have thrust this attack vector back into the spotlight, and the implications are serious.
What Is the PDF Launch Action?
The PDF specification includes a feature called the Launch action. It's designed to let documents open external applications or files. A PDF might use it to launch a spreadsheet program when you click a link, or open a supplementary file. Sounds handy, right?
The problem is that this feature can execute arbitrary commands on your system. A properly secured PDF reader should display a prominent warning before running any external program, giving users a chance to decline. But here's where things get ugly: several popular PDF applications have been found to skip this warning entirely, executing whatever code the attacker embeds without saying a word.
2025: The Year of PDF Launch Vulnerabilities
Recent months have seen a cluster of vulnerabilities affecting multiple PDF applications, all stemming from the same root cause — inadequate or missing user warnings when Launch actions are triggered.
CVE-2025-14417 — PDF Architect (CVSS 7.8)
pdfforge PDF Architect fails to warn users before executing Launch actions. An attacker can embed malicious commands that run silently when the victim opens the PDF. The vulnerability allows full remote code execution with user privileges.
CVE-2025-14415 — Soda PDF Desktop (CVSS 7.0)
Soda PDF Desktop processes Launch actions without presenting security warnings. The application runs embedded scripts or executables directly, bypassing user consent entirely.
CVE-2025-14403 — PDFsam Enhanced (CVSS 7.8)
PDFsam Enhanced lacks proper UI warnings when handling Launch actions. Reported through the Zero Day Initiative, this vulnerability allows arbitrary code execution through crafted PDF files.
All three vulnerabilities share a common classification: CWE-356 (Insufficient UI Warning of Dangerous Operations). The PDF readers know they're about to execute something potentially dangerous, but they fail to inform the user before doing so.
How the Attack Works
The exploitation chain is disturbingly simple:
- Crafting the malicious PDF: The attacker creates a PDF containing a Launch action that points to a malicious executable or script — often PowerShell, cmd.exe, or a binary dropped onto the system.
- Delivery: The PDF is delivered via email, hosted on a compromised website, or offered as a download. Social engineering tricks victims into opening it.
- Silent execution: When the victim opens the PDF in a vulnerable reader, the Launch action triggers without any warning dialog. The attacker's code runs with the same privileges as the logged-in user.
- Compromise: From there, attackers can install malware, steal credentials, move laterally across the network, or establish persistence.
The attack doesn't require administrator privileges — it runs in the context of the current user. But that's often enough. Once an attacker has a foothold on a workstation, privilege escalation is usually just a matter of time.
Detecting Malicious PDF Launch Actions
If you're analyzing suspicious PDF files, here's what to look for:
- /Launch action dictionaries: Search for
/Launchand/Actionobjects in the PDF structure - Executable references: Look for references to cmd.exe, powershell.exe, wscript.exe, cscript.exe, or other interpreters
- Unexpected child processes: Monitor PDF readers for spawning shell processes
- File writes to temp directories: Unexpected files appearing in %TEMP% or %APPDATA% after opening a PDF
You can examine PDF structure using tools like pdf-parser.py from theREMnux distribution, or open the PDF in a text editor and search for /Launch strings.
Protecting Yourself
Until vendors patch these vulnerabilities, defense-in-depth is your best strategy:
- Switch PDF readers: Adobe Reader with Protected View and some open-source readers properly warn before executing Launch actions. Check your reader's security settings.
- Application control: Use Windows AppLocker or similar tools to block PDF applications from spawning cmd.exe, powershell.exe, and other scripting interpreters.
- User awareness: Train users to avoid opening PDF files from untrusted sources, especially unexpected email attachments.
- Endpoint monitoring: Monitor for PDF reader processes spawning unusual child processes — that's a strong indicator of compromise.
- Network segmentation: Limit outbound connections from workstations to contain any breach.
What This Means for Security Teams
The PDF Launch action vulnerabilities highlight a uncomfortable truth: file formats we trust can contain hidden attack surfaces. The PDF specification is decades old, and features like Launch actions were designed in an era before modern security thinking.
For security analysts, the lesson is clear — don't treat PDFs as passive documents. Treat them as executable content that deserves scrutiny, especially when they originate from untrusted sources. With these recent CVEs affecting widely-used PDF applications, now is a good time to audit which PDF readers are deployed across your environment and verify their security configurations.
The threat isn't theoretical. Attackers are actively developing tools to craft malicious PDFs with Launch actions. The question is whether your defenses are ready.