Loading vulnerability…
CVE-2026-42853 is a command injection vulnerability in the @apostrophecms/cli package used by ApostropheCMS, affecting versions up to and including 3.6.0. The flaw is present in the apos create command, where user-supplied input collected from the password prompt is incorporated directly into a shell command without proper sanitization or escaping. Because the CLI uses attacker-controllable input in a shell execution context, crafted input can break out of the intended command structure and trigger arbitrary command execution on the host running the CLI.
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.
@apostrophecms/cli in project creation workflows where password input could be untrusted or externally influenced. Do not paste or provide attacker-controlled values to the password prompt. If use of the vulnerable CLI is unavoidable, run project creation only in isolated, low-privilege environments such as disposable containers or sandboxed developer environments, and avoid executing it on sensitive hosts.Patch, then assume compromise.
exec() with safer alternatives such as execFileSync() and supplying the password through standard input or another non-shell argument handling mechanism. At the time of publication, no patched version is known to be available.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.