CVE-2026-33154: dynaconf is a configuration management tool for Python

Q: How do I fix CVE-2026-33154?

dynaconf: upgrade to 3.2.13. Exact commands for each OS are on this page.

Q: Is CVE-2026-33154 being exploited?

CVE-2026-33154 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-33154 affect?

CVE-2026-33154 affects dynaconf. Severity is high (CVSS 7.5). 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,

Q: How urgent is CVE-2026-33154?

Priority 43/100. High severity; Public exploit reference

This month

HIGH 7.5UPGRADE

CVE-2026-33154 is a high-severity flaw (CVSS 7.5) affecting dynaconf. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.5 (High)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-94, CWE-1336, CWE-78
Published	2026-03-20
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: dynaconf

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-20 21:17 UTCPublished CVE record published
2026-06-17 10:37 UTCUpdated Record last modified

dynaconf dynaconf UPGRADE

Affected: < 3.2.13

Fixed in: 3.2.13

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy dynaconf || rpm -q dynaconf || dynaconf --version

2. UPGRADE to 3.2.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade dynaconf

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade dynaconf

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33154?

dynaconf: upgrade to 3.2.13. Exact commands for each OS are on this page.

Is CVE-2026-33154 being exploited?

CVE-2026-33154 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33154 affect?

CVE-2026-33154 affects dynaconf. Severity is high (CVSS 7.5). 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,

How urgent is CVE-2026-33154?

Priority 43/100. High severity; Public exploit reference

Software pages

Python vulnerabilities

References

← Back to latest CVEs