Yes. Django 1.7 reached end of life on 1 December 2015 (11 years ago) and no longer receives security updates.
- Released
- 3 September 2014
- Active support ends
- 1 April 2015
- Security support ends
- 1 December 2015
- Latest release
- 1.7.11 · 24 November 2015
- Long-term support
- No
What this means for your servers
New vulnerabilities in Django 1.7 are no longer fixed. Every newly published CVE that affects it stays open on your servers, and vulnerability scanners and compliance audits (PCI DSS, SOC 2, Cyber Essentials, ISO 27001) flag unsupported software as a finding. Upgrade, or isolate the machine until you can.
How to check if you’re running Django 1.7
CLI
python -m django --versionWhat to upgrade to
The newest supported long-term support release is Django 5.2, supported until 30 April 2028.
Move between LTS releases (x.2). Fix deprecation warnings on your current version first (python -Wa manage.py test), then upgrade one feature release at a time if you are far behind.
Find end-of-life software before an auditor does
Statance reads the version from official Django container image tags on your servers and raises a security finding when it goes past end of life or falls behind the latest patch, along with known CVEs from OSV.dev and CISA’s Known Exploited Vulnerabilities list. Security monitoring is included in Pro and Business. How security monitoring works.
Other Django releases
| Release | Status | Security support ends |
|---|---|---|
| Django 6.1 | Supported | 31 December 2027 |
| Django 6.0 | Security fixes only | 30 April 2027 |
| Django 5.2 | Security fixes only | 30 April 2028 |
| Django 1.10 | End of life | 2 December 2017 |
| Django 1.9 | End of life | 4 April 2017 |
| Django 1.8 | End of life | 1 April 2018 |
| Django 1.6 | End of life | 1 April 2015 |
| Django 1.5 | End of life | 2 September 2014 |
| Django 1.4 | End of life | 1 October 2015 |
All Django end-of-life dates →
FAQ
Is Django 1.7 end of life?
Yes. Django 1.7 reached end of life on 1 December 2015 (11 years ago) and no longer receives security updates.
When does Django 1.7 reach end of life?
Security support for Django 1.7 ended on 1 December 2015. Active support ended earlier, on 1 April 2015.
What should I upgrade Django 1.7 to?
Django 5.2 is the newest long-term support release that is still supported, with security updates until 30 April 2028. Move between LTS releases (x.2).
Can I keep running Django 1.7 after end of life?
It keeps working, but new vulnerabilities will not be fixed, so every newly published CVE stays open on your server. Scanners and compliance frameworks (PCI DSS, SOC 2, Cyber Essentials) treat unsupported software as a finding.
What is the latest version of Django 1.7?
The latest release in this cycle is 1.7.11, released on 24 November 2015.
Lifecycle data from endoflife.date/django, refreshed 17 November 2026. Vendors occasionally change dates; check the vendor’s own lifecycle page before making a compliance decision.
Stop tracking end-of-life dates by hand.
Statance flags end-of-life and vulnerable software on every server automatically.