Loading vulnerability…
Maple up to and including version 13 contains unsafe behavior in its Maplet framework whereby embedded commands in a .maplet file are executed automatically when the file is opened. This bypasses the normal security restrictions applied to standard Maple worksheets that would otherwise limit or prevent code execution. An attacker can craft a malicious .maplet file so that opening it triggers execution of attacker-controlled commands.
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 (maple_maplet.rb) that exploits a vulnerability in Maplesoft Maple (up to version 13) on Windows and Linux. The exploit leverages Maple's Maplet file format, which allows embedded commands to be executed automatically when a .maplet file is opened. The module generates a malicious .maplet file containing a payload (either as an executable or a command), which is written to disk and executed when the victim opens the file in Maple. The exploit supports multiple platforms (Windows x86/x64, Linux x86/x64, and generic command execution) and allows the attacker to specify a template file to append the malicious content to. The main attack vector is local, requiring user interaction (the victim must open the malicious file). The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The only fingerprintable endpoints are the generated .maplet file and any optional template file used.
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 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.