Complete end-of-life dates, support windows, and security status for all Django versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.3 | 1.3.7 | Mar 23, 2011 | Feb 26, 2013 | 4820 days past EOL | EOL |
| 1.4 | 1.4.22 | Mar 23, 2012 | Oct 1, 2015 | 3873 days past EOL | EOL |
| 1.5 | 1.5.12 | Feb 26, 2013 | Sep 2, 2014 | 4267 days past EOL | EOL |
| 1.6 | 1.6.11 | Nov 6, 2013 | Apr 1, 2015 | 4056 days past EOL | EOL |
| 1.7 | 1.7.11 | Sep 3, 2014 | Dec 1, 2015 | 3812 days past EOL | EOL |
| 1.8 | 1.8.19 | Apr 1, 2015 | Apr 1, 2018 | 2960 days past EOL | EOL |
| 1.9 | 1.9.13 | Dec 1, 2015 | Apr 4, 2017 | 3322 days past EOL | EOL |
| 1.10 | 1.10.8 | Aug 1, 2016 | Dec 2, 2017 | 3080 days past EOL | EOL |
| 1.11 LTS | 1.11.29 | Apr 4, 2017 | Apr 1, 2020 | 2229 days past EOL | EOL |
| 2.0 | 2.0.13 | Dec 2, 2017 | Apr 1, 2019 | 2595 days past EOL | EOL |
| 2.1 | 2.1.15 | Aug 1, 2018 | Dec 2, 2019 | 2350 days past EOL | EOL |
| 2.2 LTS | 2.2.28 | Apr 1, 2019 | Apr 11, 2022 | 1489 days past EOL | EOL |
| 3.0 | 3.0.14 | Dec 2, 2019 | Apr 6, 2021 | 1859 days past EOL | EOL |
| 3.1 | 3.1.14 | Aug 4, 2020 | Dec 7, 2021 | 1614 days past EOL | EOL |
| 3.2 LTS | 3.2.25 | Apr 6, 2021 | Apr 1, 2024 | 768 days past EOL | EOL |
| 4.0 | 4.0.10 | Dec 7, 2021 | Apr 1, 2023 | 1134 days past EOL | EOL |
| 4.1 | 4.1.13 | Aug 3, 2022 | Dec 1, 2023 | 890 days past EOL | EOL |
| 4.2 LTS | 4.2.30 | Apr 3, 2023 | Apr 7, 2026 | 32 days past EOL | EOL |
| 5.0 | 5.0.14 | Dec 4, 2023 | Apr 2, 2025 | 402 days past EOL | EOL |
| 5.1 | 5.1.15 | Aug 7, 2024 | Dec 3, 2025 | 157 days past EOL | EOL |
| 5.2 LTS | 5.2.14 | Apr 2, 2025 | Apr 30, 2028 | 722 days remaining | Active |
| 6.0 | 6.0.5 | Dec 3, 2025 | Apr 30, 2027 | 356 days remaining | Active |
When a Django version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Django should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Django versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Extended security support for Django beyond official EOL dates.
Learn More →Upload your dependency file and scan your entire stack for EOL risk in seconds. Free, no account required.
Stack Scanner →