BREW-DYNACONF-CVE-2026-33154 (GHSA-PXRR-HQ57-Q35P)

Vulnerability from osv_homebrew – Published: 2026-08-13 16:44 – Updated: 2026-10-12 17:07 – Source website
VLAI
Summary
dynaconf Affected by Remote Code Execution (RCE) via Insecure Template Evaluation in @jinja Resolver
Details

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
7.5 (High)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
References
To clipboard 

{
  "affected": [
    {
      "ecosystem_specific": {
        "fix": "bump",
        "range_state": "fixed",
        "upstream_fixed_in": "3.2.13"
      },
      "package": {
        "ecosystem": "Homebrew",
        "name": "dynaconf",
        "purl": "pkg:brew/dynaconf"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.1.7"
            },
            {
              "fixed": "3.2.13"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "confidence": "high",
    "source": "matched",
    "strategy": "git",
    "upstream_evidence": [
      {
        "ecosystem": "GIT",
        "key": "https://github.com/dynaconf/dynaconf",
        "name": "https://github.com/dynaconf/dynaconf",
        "strategy": "git",
        "subject_version": "3.3.5"
      },
      {
        "ecosystem": "PyPI",
        "key": "pkg:pypi/dynaconf@3.3.5",
        "name": "dynaconf",
        "strategy": "registry",
        "subject_version": "3.3.5"
      },
      {
        "ecosystem": "Debian",
        "key": "Debian/python-dynaconf",
        "name": "python-dynaconf",
        "strategy": "distro"
      },
      {
        "ecosystem": "GIT",
        "key": "upstream:https://github.com/dynaconf/dynaconf",
        "name": "https://github.com/dynaconf/dynaconf",
        "strategy": "distro",
        "subject_version": "3.3.5"
      },
      {
        "ecosystem": "PyPI",
        "key": "upstream:pkg:pypi/dynaconf@3.3.5",
        "name": "dynaconf",
        "strategy": "distro",
        "subject_version": "3.3.5"
      },
      {
        "ecosystem": "Ubuntu",
        "key": "Ubuntu/python-dynaconf",
        "name": "python-dynaconf",
        "strategy": "distro"
      }
    ]
  },
  "details": "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.",
  "id": "BREW-dynaconf-CVE-2026-33154",
  "modified": "2026-10-12T17:07:32Z",
  "published": "2026-08-13T16:44:51Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/dynaconf/dynaconf/releases/tag/3.2.13"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/33xxx/CVE-2026-33154.json"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/dynaconf/dynaconf/security/advisories/GHSA-pxrr-hq57-q35p"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-33154"
    },
    {
      "type": "FIX",
      "url": "https://github.com/dynaconf/dynaconf/commit/2fbb45ee36b8c0caa5b924fe19f3c1a5e8603fa7"
    }
  ],
  "schema_version": "1.7.3",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "dynaconf Affected by Remote Code Execution (RCE) via Insecure Template Evaluation in @jinja Resolver",
  "upstream": [
    "GHSA-pxrr-hq57-q35p",
    "CVE-2026-33154",
    "PYSEC-2026-2147"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.