HighGHSA-8r7q-cvjq-x353CVE-2014-1402PYSEC-2014-8

Incorrect Privilege Assignment in Jinja2

Published 14 May 2022 · Updated 24 Sept 2024

Is your project on an affected jinja2?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

jinja2PyPI
Affected
<2.7.2
Fixed in
2.7.2
Update to the fixed version for your release line, for example:pip install 'jinja2>=2.7.2'

Details

The default configuration for bccache.FileSystemBytecodeCache in Jinja2 before 2.7.2 does not properly create temporary files, which allows local users to gain privileges via a crafted .cache file with a name starting with __jinja2_ in /tmp.

Is GHSA-8r7q-cvjq-x353 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected jinja2, and gives you the command that fixes it.

More advisories for jinja2

  • MediumCVE-2025-27516Jinja2 vulnerable to sandbox breakout through attr filter selecting format method · 5 Mar 2025
  • MediumCVE-2024-56326Jinja has a sandbox breakout through indirect reference to format method · 23 Dec 2024
  • MediumCVE-2024-56201Jinja has a sandbox breakout through malicious filenames · 23 Dec 2024
  • MediumCVE-2024-34064Jinja vulnerable to HTML attribute injection when passing user input as keys to xmlattr filter · 6 May 2024
  • MediumCVE-2024-22195Jinja vulnerable to HTML attribute injection when passing user input as keys to xmlattr filter · 11 Jan 2024
  • MediumCVE-2014-0012Insecure Temporary File in Jinja2 · 17 May 2022
All 10 advisories for jinja2

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.