NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
HIGH severity

CVE-2014-1418 — django

HIGHFix: django/django@1abcf3a

CVE-2014-1418 is a high-severity (CVSS 7.4) vulnerability in django. A fix is available for django — see the affected versions and patch details below.

Django Vulnerable to Cache Poisoning

Also known asGHSA-q7q2-qf2q-rw3wPYSEC-2014-19
Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
2.6%probability of exploitation in next 30 days
Lower Risk+0.05%
Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk
0.00%1.08%2.17%3.25%0.5%2.6%May 26Sep 26Nov 26

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

4 pkgs affected
🐍django🐍django🐍django🐍django

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

Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1) Vary: Cookie or (2) Cache-Control header in responses, which allows remote attackers to obtain sensitive information or poison the cache via a request from certain browsers.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIdjango≥ 1.4&&< 1.4.131.4.13pip install --upgrade 'django==1.4.13'
🐍PyPIdjango≥ 1.5&&< 1.5.81.5.8pip install --upgrade 'django==1.5.8'
🐍PyPIdjango≥ 1.6&&< 1.6.51.6.5pip install --upgrade 'django==1.6.5'
🐍PyPIdjango≥ 1.7a1&&< 1.7b41.7b4pip install --upgrade 'django==1.7b4'

Affected Products

2 products · 39 configurations
OS
ubuntu linuxcanonical
5 versions
10.0412.0412.1013.1014.04
Application
djangodjangoproject
26 versions
1.41.4.11.4.21.4.41.4.51.4.61.4.71.4.81.4.91.4.101.4.111.4.12

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

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

  3. 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.

Frequently Asked Questions

Django 1.4 before 1.4.13, 1.5 before 1.5.8, 1.6 before 1.6.5, and 1.7 before 1.7b4 does not properly include the (1) Vary: Cookie or (2) Cache-Control header in responses, which allows remote attackers to obtain sensitive information or poison the cache via a request from certain browsers.
O3 Security · Impact-Aware SCA

Is CVE-2014-1418 in your dependencies?

Find it across PyPI, including transitive dependencies.

CVE-2014-1418: django Info Disclosure — Fixed in 1.4.13