high CVSS 7.5 EPSS <0.1%

CVE-2026-33154·Python vulnerability

dynaconf is a configuration management tool for Python. Prior to version 3.2.13, 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. This issue has been patched in version 3.2.13.

Severity
high
Software
Python
Fixed in
3.2.13
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at <0.1% — higher than 16% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-33154 scores 7.5 on CVSS, so a successful attack would be serious — but at <0.1%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 3.2.13

Fixed in: 3.2.13

How to fix this CVE

Upgrade Dynaconf to version 3.2.13 or later to patch the Server-Side Template Injection vulnerability in the @Jinja resolver. If you use Dynaconf for configuration management in Python applications, ensure jinja2-templated config values are no longer evaluated in an unsafe context. Patch your Python environment and redeploy affected applications immediately.

sudo dnf update python3-dynaconf && pip3 install --upgrade dynaconf>=3.2.13

Defensia detects this vulnerability

How to check if you are affected

  1. Run `pip3 show dynaconf` to retrieve the installed Dynaconf version and compare against 3.2.13
  2. Search your application code for @Jinja resolver usage in configuration files: `grep -r '@Jinja' /path/to/app/config`
  3. Check if jinja2 is installed as a dependency: `pip3 show jinja2` — if present, template injection is possible
  4. After patching, re-run `pip3 show dynaconf` to confirm version is 3.2.13 or higher

FAQ

What is CVE-2026-33154?

CVE-2026-33154 is a Server-Side Template Injection flaw in Dynaconf's @Jinja resolver that allows authenticated attackers to execute arbitrary code by injecting Jinja2 template expressions into configuration values when jinja2 is installed.

Is CVE-2026-33154 being actively exploited?

No, CVE-2026-33154 is not currently listed on the CISA KEV catalog and no public exploits have been disclosed, though the vulnerability has a high CVSS score of 7.5.

What versions of Python are affected by CVE-2026-33154?

All versions of Dynaconf prior to 3.2.13 are vulnerable; the exact affected Dynaconf release range is unknown, but upgrading to 3.2.13 or later eliminates the risk.

How do I check if my server is vulnerable to CVE-2026-33154?

Run `pip3 show dynaconf | grep Version` — if the version is below 3.2.13 and jinja2 is installed, your system is vulnerable.

Does Defensia detect CVE-2026-33154?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Dynaconf is installed on a monitored server, CVE-2026-33154 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2026-25632CVSS 10EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.
CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-33154. Free for 1 server.

Get started free