Dynaconf versions prior to 3.2.13 contain a server-side template injection vulnerability in the @Jinja resolver. When the jinja2 package is installed, template expressions embedded in configuration values are evaluated without a sandboxed environment. Malicious configuration expressions can consequently cause arbitrary code execution. The vulnerability is fixed in Dynaconf 3.2.13.
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 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.
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Server-side template injection vulnerability in Dynaconf that allows arbitrary code execution. The advisory supplies an updated python3.12-dynaconf package.
A server-side template injection vulnerability in Dynaconf permits arbitrary code execution. Updated Dynaconf packages are supplied in the advisory.
A server-side template injection vulnerability in Dynaconf allows arbitrary code execution. The advisory provides fixes through the Satellite 6.16.14 update.
A Dynaconf arbitrary code execution vulnerability caused by server-side template injection.
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.