Markdown Preview Enhanced versions 0.6.5 and 0.19.6 for VSCode and Atom are affected by a command injection vulnerability in the PDF file import function. The vulnerability allows an attacker to inject arbitrary commands that are executed in the context of the application when importing a PDF file.
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 documents and demonstrates a command injection vulnerability (CVE-2022-45025) in the Mume library, which is used by the Markdown Preview Enhanced extensions for VSCode and Atom. The vulnerability arises from the use of Node.js's spawn function with the {shell: true} option, allowing shell command injection via specially crafted @import statements in Markdown files. The repository contains a detailed README.md explaining the vulnerability, a proof-of-concept (PoC) payload, and a sample malicious Markdown file (examples/malicious.md) that triggers the exploit by opening the Calculator app on macOS. The exploit is triggered when a victim opens a malicious Markdown file with the vulnerable extension, resulting in arbitrary command execution. The repository does not contain exploit code in a programming language, but provides clear PoC payloads and usage instructions. The main attack vector is local, requiring user interaction (opening a malicious file). The repository also references an external endpoint for loading the malicious payload via a remote Markdown file.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.