High, CVSS 7.5PyPIAmendedPublished
dynaconf Affected by Remote Code Execution (RCE) via Insecure Template Evaluation in @jinja Resolver
CVE-2026-33154 · GHSA-pxrr-hq57-q35p
- Affected
- PyPI dynaconf <= 3.2.12
- Fixed in
- 3.2.13· Vendor fix available
- Issue
- Dynaconf is vulnerable to Server-Side Template Injection (SSTI) due to unsafe template evaluation in the @jinja resolver. When the jinja2 package is installed, Dynaconf evaluates template expressions embedded in configuration values without a sandboxed environment. If an attacker can influence configuration sources such as: environment variables .env files container environment configuration CI/CD secrets they can execute arbitrary OS commands on the host system. In addition, the @format resolver allows object graph traversal, which may expose sensitive runtime objects and environment variables. Details The vulnerability arises because Dynaconf's string resolvers lack proper security boundaries. 1. @jinja Resolver The @jinja resolver renders templates using full Jinja2 evaluation. However, the rendering context is not sandboxed, which allows attackers to access Python's internal attributes. Using objects such as cycler, attackers can reach Python's globals and import the os…
Recommended action: Upgrade to 3.2.13 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.