python3-jinja2 vulnerabilities — 4 matching vulnerabilities
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed — no installation and no source-code access required.
| Severity | Vulnerability | Package | Ecosystem | Disclosed | Fixed version |
|---|---|---|---|---|---|
| Unrated | Critical Security Update for python3-jinja2: Jinja Sandbox Breakout Vulnerability |
python3-jinja2
|
AlmaLinux | 31 Mar 2025 | 2.11.3-8.el9_5 |
| Unrated | Critical Security Update for python-jinja2: Sandbox Breakout Vulnerability |
python3-jinja2
|
AlmaLinux | 23 Jan 2025 | 2.11.3-7.el9_5 |
| Unrated | Moderate Vulnerability in python-jinja2: Security Update Required |
python3-jinja2
|
AlmaLinux | 12 Nov 2024 | 2.11.3-6.el9 |
| Unrated | Moderate: python-jinja2 security update |
python3-jinja2
|
AlmaLinux | 30 Apr 2024 | 2.11.3-5.el9 |
Questions
Searching the database
How do I search for a CVE or a package?
Type a CVE id, package name, ecosystem or keyword into the search field. Results include the severity, the affected package, the ecosystem, the disclosure date and the fixed version.
Can I filter by severity or by whether a fix exists?
Yes. The filters on the left narrow the list to critical, high, medium or low vulnerabilities, to a single ecosystem, and to vulnerabilities that have a fix available or none yet.
What does "No fix published" mean?
No patched version has been released for that vulnerability yet. The vulnerability page still shows the affected range and any workaround that can reduce exposure in the meantime.