dynaconf は @jinja Resolver における不安全なテンプレート評価によるリモートコード実行 (RCE) に影響

The core of this vulnerability lies in Dynaconf's @jinja resolver, which processes template expressions without proper sandboxing when the jinja2 package is installed. An attacker who can manipulate configuration sources—such as environment variables, .env files, container environment configurations, or CI/CD secrets—can inject malicious template code. This injected code, when evaluated by Dynaconf, can lead to arbitrary command execution on the host system. The potential impact is severe, allowing attackers to gain complete control over the affected server, steal sensitive data, or pivot to other systems within the network. The @format resolver also introduces object graph traversal, potentially exposing sensitive runtime objects and environment variables, further increasing the attack surface.

Applications and systems that rely on Dynaconf for configuration management, particularly those deployed in environments where configuration sources (environment variables, .env files, CI/CD pipelines) are not adequately secured, are at significant risk. Shared hosting environments and applications using containerized deployments are also particularly vulnerable due to the ease with which configuration values can be manipulated.

• python / server:

import subprocess
import os

# Check Dynaconf version
result = subprocess.run(['pip', 'show', 'dynaconf'], capture_output=True, text=True)
output = result.stdout
if 'Version:' in output:
    version = output.split('Version:')[1].strip().split('\n')[0]
    if version <= '3.2.9':
        print(f'Dynaconf version is vulnerable: {version}')
else:
    print('Dynaconf is not installed or version cannot be determined.')

• linux / server:

# Check Dynaconf version using pip
python3 -c "import dynaconf; print(dynaconf.__version__)"
# Check for suspicious processes
ps aux | grep -i jinja

• generic web: Inspect application logs for any errors or warnings related to Jinja2 template evaluation or unexpected command execution.

1. 2026-03-18Disclosure

   disclosure

1. 予約済み2026-03-17
2. 公開日2026-03-18
3. 更新日2026-04-14
4. EPSS 更新日2026-03-28

The primary mitigation for CVE-2026-33154 is to upgrade Dynaconf to version 3.2.13 or later, which includes the necessary fixes to prevent unsafe template evaluation. If an immediate upgrade is not feasible due to compatibility issues or breaking changes, consider temporarily restricting access to configuration sources that attackers could potentially manipulate. Implement strict input validation and sanitization on all configuration values to prevent malicious template code from being injected. If possible, disable the @jinja resolver entirely if it is not essential for your application. Monitor system logs for suspicious activity related to template evaluation or command execution. After upgrading, confirm the fix by attempting to inject a simple Jinja2 template expression into a configuration value and verifying that it is not evaluated.