Is Django 1.6.11 patched?
Current stable (6.0.6): 100/100
1.6.11 has 2 open critical-or-high vulnerabilities. Run 1.11.29 or later to clear them. See what 1.11.29 fixes →
Summary iPlain-English security status for Django 1.6.11, built from its CVEs, active-exploitation data, end-of-life date and latest release.
Django 1.6.11 is part of the 1.6 release line. 6 known vulnerabilities affect it. The minimum safe version is 1.11.29 — upgrade to it or later to clear the open critical/high issues. The 1.6 line reached end-of-life on 2015-04-01, so it no longer receives security patches. The latest supported Django release is 6.0.6.
Known issues affecting 1.6.11
Exploited first, then by exploitation probability.
CVE-2019-19844 CRITICAL EPSS 35% → fixed in 2.2.9 CVE-2016-7401 HIGH EPSS 6% → see advisory CVE-2016-6186 MEDIUM EPSS 6% → see advisory CVE-2015-8213 MEDIUM EPSS 4% → see advisory CVE-2021-33203 MEDIUM EPSS 3% → fixed in 3.2.4 CVE-2015-2241 MEDIUM EPSS 2% → see advisoryOther Django versions
Check another release line of Django.
Frequently asked
Is Django 1.6.11 patched?
Django 1.6.11 is end-of-life and no longer receives security patches. Move to 6.0.6.
What version should I upgrade Django 1.6.11 to?
Upgrade Django 1.6.11 to at least 1.11.29 to clear its 2 open critical-or-high vulnerabilities.
When does Django 1.6 reach end-of-life?
Django 1.6 reached end-of-life on 2015-04-01 and no longer receives security patches.
What is the latest version of Django?
The latest supported Django release is 6.0.6.
Is Django 1.6.11 still receiving security updates?
No — Django 1.6.11 is on the 1.6 line, which reached end-of-life on 2015-04-01 and no longer receives security updates. Upgrade to 6.0.6 or later to stay supported.
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against Django's official advisory before you patch or upgrade — Django official site ↗