Django End of Life Dates

framework

Developers leveraging Python for web development often rely on a robust framework to streamline their workflow, and Django has been a stalwart option since its inception. Created to facilitate rapid development and clean design, Django's model–template–views architectural pattern has made it a favorite among developers. With the Django Software Foundation at the helm, maintaining and supporting this framework, developers can trust that they have a reliable foundation for their projects. The fact that Django has been around for a while, with a substantial number of versions released over the years, is a testament to its enduring popularity and the active community that contributes to its growth.

The landscape of Django's versions reveals a story of continuous evolution, with a total of 22 versions released to date. Of these, 20 have reached their end-of-life, indicating that they no longer receive security updates or support. Currently, only 2 versions remain active, with the latest stable version being 6.0.6. Looking ahead, version 6.0 is slated to reach its end-of-life on 2027-04-30, marking an important milestone for developers who are still using this version. This transition underscores the importance of staying up-to-date with the latest versions to ensure the security and integrity of their applications. The most recent end-of-life transition occurred on 2026-04-07, when version 4.2 ceased to be supported.

From a security standpoint, Django has been tracked for 55 known vulnerabilities, with 3 of these being critical. Version 5.2 is notably the most affected, with 21 vulnerabilities attributed to it. This highlights the need for developers to be vigilant about the versions they use and to prioritize updates to mitigate potential risks. Given the Known Exploited Vulnerabilities status that may apply to certain versions, it is crucial for developers to take proactive action to protect their applications. By migrating to the latest stable version, such as 6.0.6, developers can ensure they have the latest security patches and features, thereby safeguarding their projects against known and emerging threats.

Last updated: Oct 23, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
6.1 Aug 5, 2026Apr 30, 2027Dec 31, 2027in 434d6.1.2—Active
6.0 Dec 3, 2025Aug 4, 2026Apr 30, 2027in 189d6.0.9Active
5.2 LTSApr 2, 2025Dec 3, 2025Apr 30, 2028in 555d5.2.18Active
5.1 Aug 7, 2024Apr 2, 2025Dec 3, 2025324d ago5.1.15EOL
5.0 Dec 4, 2023Aug 7, 2024Apr 2, 2025569d ago5.0.14EOL
4.2 LTSApr 3, 2023Dec 4, 2023Apr 7, 2026199d ago4.2.30EOL
4.1 Aug 3, 2022Apr 5, 2023Dec 1, 20231057d ago4.1.13EOL
4.0 Dec 7, 2021Aug 3, 2022Apr 1, 20231301d ago4.0.10EOL
3.2 LTSApr 6, 2021Dec 7, 2021Apr 1, 2024935d ago3.2.25EOL
3.1 Aug 4, 2020Apr 6, 2021Dec 7, 20211781d ago3.1.14EOL
3.0 Dec 2, 2019Aug 3, 2020Apr 6, 20212026d ago3.0.14EOL
2.2 LTSApr 1, 2019Dec 2, 2019Apr 11, 20221656d ago2.2.28EOL
2.1 Aug 1, 2018Apr 1, 2019Dec 2, 20192517d ago2.1.15EOL
2.0 Dec 2, 2017Aug 1, 2018Apr 1, 20192762d ago2.0.13EOL
1.11 LTSApr 4, 2017Dec 2, 2017Apr 1, 20202396d ago1.11.29EOL
1.10 Aug 1, 2016Apr 4, 2017Dec 2, 20173247d ago1.10.8EOL
1.9 Dec 1, 2015Aug 1, 2016Apr 4, 20173489d ago1.9.13EOL
1.8 Apr 1, 2015Dec 1, 2015Apr 1, 20183127d ago1.8.19EOL
1.7 Sep 3, 2014Apr 1, 2015Dec 1, 20153979d ago1.7.11EOL
1.6 Nov 6, 2013Sep 2, 2014Apr 1, 20154223d ago1.6.11EOL
1.5 Feb 26, 2013Nov 6, 2013Sep 2, 20144434d ago1.5.12EOL
1.4 Mar 23, 2012Feb 26, 2013Oct 1, 20154040d ago1.4.22EOL
1.3 Mar 23, 2011Mar 23, 2012Feb 26, 20134987d ago1.3.7EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions