Loading vulnerability…
CVE-2026-53951 is a trust-validation bypass in the Copier library and CLI application affecting versions 9.5.0 through 9.15.1. The flaw is in handling of the trust setting in copier/_settings.py, where a template reference is checked against a trusted prefix using a raw str.startswith comparison before path or URL normalization. Later, when the template is actually fetched, Copier normalizes the reference using Path.resolve() for local paths and standard dot-segment removal for HTTPS paths. Because the trust decision is made on the non-normalized string, an attacker can supply a template reference containing .. segments that textually matches a trusted prefix but resolves to a different attacker-controlled template. That template is then incorrectly treated as trusted, allowing unsafe features such as tasks, migrations, and jinja_extensions to execute without the normal --trust confirmation. The result is arbitrary command execution in the context of the user running Copier.
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.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.