Django · Lifecycle Status

Django End of Life (EOL) Dates & Support Timeline

Q: What is the end-of-life date for Django?

The next Django version reaching EOL is 6.0 on April 30, 2027. See the full table above for all version EOL dates.

Q: When is the Django support end date?

The next Django support end date is April 30, 2027, when version 6.0 reaches end of support. Each version has its own support end date — see the table above for every version's date.

Q: What is the latest supported version of Django?

The latest active version of Django is 6.0.7. Always verify against the table above as support windows can change.

Q: Does Django track end-of-life by point release (e.g. Django 6.0.1, Django 6.0.2)?

No — Django end-of-life dates apply to the entire 6.0.x release series, not individual point releases. A point release like Django 6.0.1 or Django 6.0.2 shares the same EOL date as Django 6.0. Security patches stop for the entire 6.0.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.

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.

📅 Get reminded before Django 6.0 reaches EOL on April 30, 2027 — alerts 90, 30 & 7 days out.

Google →

Latest Active

6.0.7

6.0 series

Next EOL

6.0

Apr 30, 2027

Active Versions

of 22 total

EOL Versions

no longer patched

Medium Risk

EOL Risk Score™ How is this calculated? →

EOL Recency

30/40

Attack Surface

20/30 High tier

CISA KEV Exposure

0/20 Not in KEV

Extended Support

0/10 Available

EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →

Release Cycle Timeline

■ EOL ■ Warning ■ Active ┊ Today

All Versions

Version	Latest Release	Release Date	EOL Date	Days	Status
1.3	1.3.7	Mar 23, 2011	Feb 26, 2013	4885 days past EOL	EOL
1.4	1.4.22	Mar 23, 2012	Oct 1, 2015	3938 days past EOL	EOL
1.5	1.5.12	Feb 26, 2013	Sep 2, 2014	4332 days past EOL	EOL
1.6	1.6.11	Nov 6, 2013	Apr 1, 2015	4121 days past EOL	EOL
1.7	1.7.11	Sep 3, 2014	Dec 1, 2015	3877 days past EOL	EOL
1.8	1.8.19	Apr 1, 2015	Apr 1, 2018	3025 days past EOL	EOL
1.9	1.9.13	Dec 1, 2015	Apr 4, 2017	3387 days past EOL	EOL
1.10	1.10.8	Aug 1, 2016	Dec 2, 2017	3145 days past EOL	EOL
1.11 LTS	1.11.29	Apr 4, 2017	Apr 1, 2020	2294 days past EOL	EOL
2.0	2.0.13	Dec 2, 2017	Apr 1, 2019	2660 days past EOL	EOL
2.1	2.1.15	Aug 1, 2018	Dec 2, 2019	2415 days past EOL	EOL
2.2 LTS	2.2.28	Apr 1, 2019	Apr 11, 2022	1554 days past EOL	EOL
3.0	3.0.14	Dec 2, 2019	Apr 6, 2021	1924 days past EOL	EOL
3.1	3.1.14	Aug 4, 2020	Dec 7, 2021	1679 days past EOL	EOL
3.2 LTS	3.2.25	Apr 6, 2021	Apr 1, 2024	833 days past EOL	EOL
4.0	4.0.10	Dec 7, 2021	Apr 1, 2023	1199 days past EOL	EOL
4.1	4.1.13	Aug 3, 2022	Dec 1, 2023	955 days past EOL	EOL
4.2 LTS	4.2.30	Apr 3, 2023	Apr 7, 2026	97 days past EOL	EOL
5.0	5.0.14	Dec 4, 2023	Apr 2, 2025	467 days past EOL	EOL
5.1	5.1.15	Aug 7, 2024	Dec 3, 2025	222 days past EOL	EOL
5.2 LTS	5.2.16	Apr 2, 2025	Apr 30, 2028	657 days remaining	Active
6.0	6.0.7	Dec 3, 2025	Apr 30, 2027	291 days remaining	Active

What does Django end of life mean for your organization?

When a version of Django 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.

Extended Support Options

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.

endoflife.ai

Get Django Support Options

Django has 20 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.

Get My Support Options →

Frequently Asked Questions

What is the end-of-life date for Django?

The next Django version reaching EOL is 6.0 on April 30, 2027. See the full table above for all version EOL dates.

When is the Django support end date?

The next Django support end date is April 30, 2027, when version 6.0 reaches end of support. Each version has its own support end date — see the table above for every version's date.

What is the latest supported version of Django?

The latest active version of Django is 6.0.7. Always verify against the table above as support windows can change.

What happens when Django reaches end of life?

When Django reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.

How do I check if I'm running an EOL version of Django?

Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.

Is there extended support available for EOL Django versions?

Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Does Django track end-of-life by point release (e.g. Django 6.0.1, Django 6.0.2)?

No — Django end-of-life dates apply to the entire 6.0.x release series, not individual point releases. A point release like Django 6.0.1 or Django 6.0.2 shares the same EOL date as Django 6.0. Security patches stop for the entire 6.0.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.

Deep Dive

Full Guide

Django End of Life: LTS vs Standard Releases and Version Support Dates

→

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →