In libslic3r/GCode/PostProcessor.cpp in Prusa PrusaSlicer through 2.6.1, a crafted 3mf project file can execute arbitrary code on a host where the project is sliced and G-code exported.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
Small two-file exploit repository containing a README and a Bash payload. The repository targets a vulnerable Linux version of PrusaSlicer and describes a local/file-based privilege-escalation workflow using a malicious .3mf project file. According to the README, the victim must be able to run PrusaSlicer with sudo, place exploit.sh at /tmp/exploit.sh, customize the callback IP/PORT, and then open 'evil.3mf' with 'sudo ./prusaslicer -s evil.3mf'. The only code file, exploit.sh, is a minimal Bash reverse shell using /dev/tcp to connect back to an attacker listener. Overall, this is a straightforward operational PoC for arbitrary code execution as root via malicious file processing, with a hardcoded payload path and manually configurable callback endpoint.
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.
1 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.