How severe is CVE-2014-1402?

CVE-2014-1402 has a CVSS score of 8.4/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2014-1402?

CVE-2014-1402 affects the following packages: jinja2 (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2014-1402?

Update jinja2 to 2.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1402 is resolved across your whole dependency graph.

How do I detect CVE-2014-1402 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jinja2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-1402 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2014-1402 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-1402 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-1402?

CVE-2014-1402 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 32th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-1402?

CVE-2014-1402 is classified as CWE-264 (CWE-264). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-1402 published, and has it been updated?

CVE-2014-1402 was published on May 19, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

CVE-2014-1402 — jinja2

HIGH

CVE-2014-1402 is a high-severity (CVSS 8.4) CWE-264 vulnerability in jinja2. A fix is available for jinja2 — see the affected versions and patch details below.

Incorrect Privilege Assignment in Jinja2

Also known asGHSA-8r7q-cvjq-x353PYSEC-2014-8

Published

May 19, 2014

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 29, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍jinja2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`jinja2`	all versions	2.7.2`pip install --upgrade 'jinja2==2.7.2'`

Affected Products

1 product · 19 configurations

Application

jinja2pocoo

≤ 2.7.1

17 versions

2.02.12.1.12.22.2.12.32.3.12.42.4.12.52.5.12.5.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jinja2, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jinja2 to 2.7.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1402 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Product	Fixed in	Advisory
Red Hat Enterprise Linux 6	`python-jinja2-0:2.2.1-2.el6_5`	RHSA-2014:0747
Red Hat Software Collections 1 for Red Hat Enterprise Linux 6	`python27-python-jinja2-0:2.6-10.el6`	RHSA-2014:0748

Ubuntu

USN-2301-1Ubuntu

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-1402 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works