<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 09:32:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-33154 — dynaconf Affected by Remote Code Execution (RCE) via Insecure Template Evaluation in @jinja Resolver</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-33154</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dynaconf&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; dynaconf&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-33154</guid>
    </item>
    <item>
      <title>GHSA-pxrr-hq57-q35p — dynaconf Affected by Remote Code Execution (RCE) via Insecure Template Evaluation in @jinja Resolver</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-pxrr-hq57-q35p</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dynaconf&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability arises because Dynaconf&amp;#39;s string resolvers lack proper security boundaries.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s internal attributes.
Using objects such as cycler, attackers can reach Python&amp;#39;s __globals__ and import the os module.&lt;/p&gt;
&lt;p&gt;Example attack path
cycler
 → __init__
 → __globals__
 → os
 → popen()
This leads to arbitrary command execution.&lt;/p&gt;
&lt;p&gt;2. @format Resolver
The @format resolver performs Python string formatting using internal objects.
This allows attackers to traverse Python&amp;#39;s object graph and access sensitive runtime objects.
Example traversal:
{this.__class__.__init__.__globals__[os].environ}
This can expose
- API keys
- database credentials
- internal service tokens
- environment secrets&lt;/p&gt;
&lt;p&gt;##…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dynaconf&lt;/p&gt;
&lt;p&gt;### 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;### Details
The vulnerability arises because Dynaconf&amp;#39;s string resolvers lack proper security boundaries.&lt;/p&gt;
&lt;p&gt;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&amp;#39;s internal attributes.
Using objects such as cycler, attackers can reach Python&amp;#39;s __globals__ and import the os module.&lt;/p&gt;
&lt;p&gt;Example attack path
cycler
 → __init__
 → __globals__
 → os
 → popen()
This leads to arbitrary command execution.&lt;/p&gt;
&lt;p&gt;2. @format Resolver
The @format resolver performs Python string formatting using internal objects.
This allows attackers to traverse Python&amp;#39;s object graph and access sensitive runtime objects.
Example traversal:
{this.__class__.__init__.__globals__[os].environ}
This can expose
- API keys
- database credentials
- internal service tokens
- environment secrets&lt;/p&gt;
&lt;p&gt;##…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-pxrr-hq57-q35p</guid>
    </item>
    <item>
      <title>PYSEC-2026-2147</title>
      <link>https://vulnerability.circl.lu/vuln/pysec-2026-2147</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dynaconf&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; PyPI: dynaconf&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/pysec-2026-2147</guid>
    </item>
  </channel>
</rss>
