VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

jinja2: vulnerability history, versions and safety

jinja2 is a package in the PyPI ecosystem. Vulert records 21 vulnerabilities for it across 66 releases, from May 2014 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
21 vulnerabilities recorded H3 M7 U11
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
5 in the last 12 months

Most recent disclosure 07 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jinja2 vulnerabilities

Vulert verdict on jinja2 3.1.6 i

Updated on 23 Oct 2026

Careful: 3.1.6 has 2 known vulnerabilities, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.1.6 — affected i
  • Vulnerabilities on record 21 over 12 years · 5 in the last year i
  • Latest disclosure 07 Jul 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 92,200 packages i
  • Stars 11,794 i
  • OpenSSF scorecard 5/10 i
  • Last release 19 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

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.

01 Versions

Which versions are affected

Every version Vulert tracks for jinja2, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.6 05 Mar 2025 U2 non-standard No Details →
3.1.5 21 Dec 2024 M1 U1 non-standard Yes Details →
3.1.4 05 May 2024 M3 U3 non-standard Yes Details →
3.1.3 10 Jan 2024 M4 U4 BSD-3-Clause Yes Details →
3.1.2 28 Apr 2022 M5 U5 BSD-3-Clause Yes Details →
3.1.1 25 Mar 2022 M5 U5 BSD-3-Clause Yes Details →
3.1.0 24 Mar 2022 M5 U5 BSD-3-Clause Yes Details →
3.0.3 09 Nov 2021 M5 U5 BSD-3-Clause Yes Details →
3.0.2 05 Oct 2021 M5 U5 BSD-3-Clause Yes Details →
3.0.1 18 May 2021 M5 U5 BSD-3-Clause Yes Details →
3.0.0 11 May 2021 M5 U5 BSD-3-Clause Yes Details →
3.0.0rc2 25 Apr 2021 M4 U4 BSD-3-Clause Yes Details →
3.0.0rc1 16 Apr 2021 M4 U4 BSD-3-Clause Yes Details →
2.11.3 31 Jan 2021 M4 U4 BSD-3-Clause Yes Details →
2.11.2 13 Apr 2020 M5 U5 BSD-3-Clause Yes Details →
3.0.0a1 05 Feb 2020 M4 U4 BSD-3-Clause Yes Details →
2.11.1 30 Jan 2020 M5 U5 BSD-3-Clause Yes Details →
2.11.0 27 Jan 2020 M5 U5 BSD-3-Clause Yes Details →
2.10.3 04 Oct 2019 M5 U5 BSD-3-Clause Yes Details →
2.10.2 04 Oct 2019 M5 U5 BSD-3-Clause Yes Details →
2.10.1 06 Apr 2019 M5 U5 non-standard Yes Details →
2.10.0 08 Nov 2017 H1 M5 U8 non-standard No Details →
2.9.6 03 Apr 2017 H1 M5 U6 non-standard Yes Details →
2.9.5 28 Jan 2017 H1 M5 U6 non-standard Yes Details →
2.9.4 10 Jan 2017 H1 M5 U6 non-standard Yes Details →
2.9.3 08 Jan 2017 H1 M5 U6 non-standard Yes Details →
2.9.2 08 Jan 2017 H1 M5 U6 non-standard Yes Details →
2.9.1 07 Jan 2017 H1 M5 U6 non-standard Yes Details →
2.9.0 07 Jan 2017 H1 M5 U8 non-standard No Details →
2.8.1 29 Dec 2016 H1 M5 U6 non-standard Yes Details →
2.8.0 26 Jul 2015 H2 M5 U8 non-standard No Details →
2.7.3 06 Jun 2014 H2 M5 U7 non-standard Yes Details →
2.7.2 10 Jan 2014 H2 M5 U8 non-standard Yes Details →
2.7.1 07 Aug 2013 H3 M6 U9 non-standard Yes Details →
2.7.0 20 May 2013 H3 M6 U9 non-standard No Details →
2.6.0 24 Jul 2011 H3 M6 U9 non-standard No Details →
2.5.5 18 Oct 2010 H3 M6 U9 non-standard Yes Details →
2.5.4 17 Oct 2010 H3 M6 U9 non-standard Yes Details →
2.5.3 17 Oct 2010 H3 M6 U9 non-standard Yes Details →
2.5.2 18 Aug 2010 H3 M6 U9 non-standard Yes Details →
2.5.1 17 Aug 2010 H3 M6 U9 non-standard Yes Details →
2.5.0 29 May 2010 H3 M6 U9 non-standard No Details →
2.4.1 20 Apr 2010 H3 M6 U9 non-standard Yes Details →
2.4.0 13 Apr 2010 H3 M6 U9 non-standard No Details →
2.3.1 19 Feb 2010 H3 M6 U9 non-standard Yes Details →
2.3.0 10 Feb 2010 H3 M6 U9 non-standard No Details →
2.2.1 14 Sep 2009 H3 M6 U9 non-standard Yes Details →
2.2.0 13 Sep 2009 H3 M6 U9 non-standard No Details →
2.1.1 25 Dec 2008 H3 M6 U9 non-standard Yes Details →
2.1.0 23 Nov 2008 H3 M6 U9 non-standard No Details →
2.0.0 17 Jul 2008 H3 M6 U9 non-standard No Details →
2.0.0rc1 09 Jun 2008 H3 M6 U9 non-standard No Details →
2.0rc1-py2.4-linux-i686 — H3 M6 U9 — No Details →
2.0rc1-py2.4-linux-x86_64 — H3 M6 U9 — No Details →
2.0rc1-py2.4-macosx-10.3-i386 — H3 M6 U9 — No Details →
2.0rc1-py2.4-win32 — H3 M6 U9 — No Details →
2.0rc1-py2.5-linux-i686 — H3 M6 U9 — No Details →
2.0rc1-py2.5-linux-x86_64 — H3 M6 U9 — No Details →
2.0rc1-py2.5-macosx-10.3-i386 — H3 M6 U9 — No Details →
2.0rc1-py2.5-win32 — H3 M6 U9 — No Details →
2.1-py2.4-win32 — H3 M6 U9 — No Details →
2.1-py2.5-win32 — H3 M6 U9 — No Details →
2.1-py2.6-win32 — H3 M6 U9 — No Details →
2.1.1-py2.4-win32 — H3 M6 U9 — No Details →
2.1.1-py2.5-win32 — H3 M6 U9 — No Details →
2.1.1-py2.6-win32 — H3 M6 U9 — No Details →

All 66 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2019 4
  • 2021 2
  • 2022 2
  • 2024 4
  • 2025 2
  • 2026 5

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 5 of the 21 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for jinja2

The 5 most severe of 21 vulnerabilities recorded for this package

Search all 21 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-56201: Jinja2 Template Sandbox Breakout Vulnerability 8.8 medium 3.1.5 23 Dec 2024
CVE-2024-56201: Jinja2 Template Sandbox Breakout Vulnerability 8.8 high 3.1.5 07 Jul 2026
CVE-2019-10906: Jinja2 - Sandbox Escape 8.6 high 2.10.1 10 Apr 2019
CVE-2016-10745: Jinja2 - Sandbox Escape 8.6 high 2.8.1 10 Apr 2019
CVE-2014-1402: Incorrect Privilege Assignment in Jinja2 8.4 high 2.7.2 14 May 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About jinja2

Is jinja2 safe to use?

Vulert records 21 vulnerabilities for jinja2 in PyPI: 0 critical, 3 high, 7 medium and 0 low, plus 11 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is jinja2's Vulert package health score?

Vulert scores jinja2 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of jinja2 affected?

Yes. 3.1.6, the version you would install today, has 2 known vulnerabilities, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of jinja2 should I use?

3.1.6 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does jinja2 have?

21 vulnerabilities are recorded for jinja2 in the PyPI ecosystem: 0 critical, 3 high, 7 medium and 0 low, plus 11 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jinja2 vulnerabilities disclosed?

5 vulnerabilities were recorded for jinja2 in the last 12 months, and the oldest entry in this database dates to 19 May 2014. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of jinja2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor jinja2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jinja2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.