Django 1.7 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Django 1.7 reached end of life on 1 Dec 2015. It no longer receives security fixes.
Support timeline
Official dates from the Django release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 3 Sept 2014 | — |
| End of life | 1 Dec 2015 | 10.7 years ago |
| Active support ended | 1 Apr 2015 | security fixes only after this |
| Latest release | 1.7.11 · 24 Nov 2015 | final |
The cost of staying: CVEs since end of life
108 Django vulnerabilities have been published since 1 Dec 2015. All were fixed in supported branches — 1.7 received none of them. Source: NVD.
Django CVEs published since 1.7's EOL, by year
12 of the 108 are rated critical · data refreshed 2026-08-09
Published 9 Dec 2016 · rated critical — fixed in supported branches only, never in 1.7. Details
Published 9 Aug 2019 · rated critical — fixed in supported branches only, never in 1.7. Details
Published 18 Dec 2019 · rated critical — fixed in supported branches only, never in 1.7. Details
Where to go from 1.7
Recommended target: Django 6.1 (supported until 31 Dec 2027).
The newest actively supported branch is Django 6.1 (latest release 6.1). Review docs.djangoproject.com before upgrading.
Frequently asked questions
Is Django 1.7 still safe to use?
No. Django 1.7 stopped receiving security fixes on 1 Dec 2015. Since then, 108 Django vulnerabilities have been published and fixed in supported branches — Django 1.7 received none of those fixes.
Can I still download Django 1.7?
Yes — the final release (1.7.11) generally remains available from vendor archives and OS package mirrors, but installing it means running software with known, unpatched vulnerabilities.
What should I upgrade Django 1.7 to?
Upgrade to Django 6.1, the newest actively supported branch (supported until 31 Dec 2027).