Django EOL: end-of-life dates for every Django version

Django 4.2 LTS reached end of life on 7 April 2026, and 4.2.30 was its last release. Django 5.2 LTS is supported until April 2028, 6.0 until April 2027 and 6.1 until December 2027. Django 5.0 and 5.1 have also ended. OSSeva patches Django 4.2, 5.0 and 5.1 after end of life. Dates checked against djangoproject.com and endoflife.date on 19 November 2026.

Only your email is required · An engineer replies within 1 business day · No commitment

Latest release
6.1.3
Supported lines
3
End-of-life lines
20
Next end of life
6.0 · 30 Apr 2027

Django 4.2 LTS has ended

Upgrade to 5.2 LTS, or keep Django 4.2, 5.0 and 5.1 patched

Most sites should move to Django 5.2 LTS. When Python, a database version or a third-party package holds a site on 4.2, OSSeva patches Django 4.2, 5.0 and 5.1. Other versions are assessed case by case through a version coverage check. Critical fixes ship within 48 hours and High within 7 days.

Who patches Django after end of life

OSSeva provides Django extended support: patched, signed builds for Django 5.1 and 5.0 after upstream support ends, plus 24/7 operations on the Operate tier.

Django release timeline

Active SupportSecurity SupportTodayChart shows the 14 newest lines; the table lists all.

All Django versions, release dates and end-of-life dates

VersionReleasedActive SupportSecurity SupportLatestOSSeva
6.14 months ago(5 Aug 2026)Ends in 5 months(30 Apr 2027)Ends in 1 year and 1 month(31 Dec 2027)6.1.3–
6.01 year ago(3 Dec 2025)Ended 4 months ago(4 Aug 2026)Ends in 5 months(30 Apr 2027)6.0.10–
5.2 (LTS)1 year and 8 months ago(2 Apr 2025)Ended 1 year ago(3 Dec 2025)Ends in 1 year and 5 months(30 Apr 2028)5.2.19–
5.12 years and 3 months ago(7 Aug 2024)Ended 1 year and 8 months ago(2 Apr 2025)Ended 1 year ago(3 Dec 2025)5.1.15 Patched
5.03 years ago(4 Dec 2023)Ended 2 years and 3 months ago(7 Aug 2024)Ended 1 year and 8 months ago(2 Apr 2025)5.0.14 Patched
4.2 (LTS)3 years and 8 months ago(3 Apr 2023)Ended 3 years ago(4 Dec 2023)Ended 8 months ago(7 Apr 2026)4.2.30–
4.14 years and 4 months ago(3 Aug 2022)Ended 3 years and 8 months ago(5 Apr 2023)Ended 3 years ago(1 Dec 2023)4.1.13–
4.04 years and 11 months ago(7 Dec 2021)Ended 4 years and 4 months ago(3 Aug 2022)Ended 3 years and 8 months ago(1 Apr 2023)4.0.10–
3.2 (LTS)5 years and 8 months ago(6 Apr 2021)Ended 4 years and 11 months ago(7 Dec 2021)Ended 2 years and 8 months ago(1 Apr 2024)3.2.25–
3.16 years and 4 months ago(4 Aug 2020)Ended 5 years and 8 months ago(6 Apr 2021)Ended 4 years and 11 months ago(7 Dec 2021)3.1.14–
3.07 years ago(2 Dec 2019)Ended 6 years and 4 months ago(3 Aug 2020)Ended 5 years and 8 months ago(6 Apr 2021)3.0.14–
2.2 (LTS)7 years and 8 months ago(1 Apr 2019)Ended 7 years ago(2 Dec 2019)Ended 4 years and 7 months ago(11 Apr 2022)2.2.28–
2.18 years and 4 months ago(1 Aug 2018)Ended 7 years and 8 months ago(1 Apr 2019)Ended 7 years ago(2 Dec 2019)2.1.15–
2.09 years ago(2 Dec 2017)Ended 8 years and 4 months ago(1 Aug 2018)Ended 7 years and 8 months ago(1 Apr 2019)2.0.13–
1.11 (LTS)9 years and 8 months ago(4 Apr 2017)Ended 9 years ago(2 Dec 2017)Ended 6 years and 8 months ago(1 Apr 2020)1.11.29–
1.1010 years and 4 months ago(1 Aug 2016)Ended 9 years and 8 months ago(4 Apr 2017)Ended 9 years ago(2 Dec 2017)1.10.8–
1.911 years ago(1 Dec 2015)Ended 10 years and 4 months ago(1 Aug 2016)Ended 9 years and 8 months ago(4 Apr 2017)1.9.13–
1.811 years and 8 months ago(1 Apr 2015)Ended 11 years ago(1 Dec 2015)Ended 8 years and 8 months ago(1 Apr 2018)1.8.19–
1.712 years and 3 months ago(3 Sept 2014)Ended 11 years and 8 months ago(1 Apr 2015)Ended 11 years ago(1 Dec 2015)1.7.11–
1.613 years and 1 month ago(6 Nov 2013)Ended 12 years and 3 months ago(2 Sept 2014)Ended 11 years and 8 months ago(1 Apr 2015)1.6.11–
1.513 years and 9 months ago(26 Feb 2013)Ended 13 years and 1 month ago(6 Nov 2013)Ended 12 years and 3 months ago(2 Sept 2014)1.5.12–
1.414 years and 8 months ago(23 Mar 2012)Ended 13 years and 9 months ago(26 Feb 2013)Ended 11 years and 2 months ago(1 Oct 2015)1.4.22–
1.315 years and 8 months ago(23 Mar 2011)Ended 14 years and 8 months ago(23 Mar 2012)Ended 13 years and 9 months ago(26 Feb 2013)1.3.7–

Lifecycle data from endoflife.date (MIT licence), refreshed 22 Nov 2026. Upstream policy: www.djangoproject.com. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.

Django 4.2, 5.2, 6.0 and 6.1 support dates

Django supports a series for a fixed window, and only LTS releases get the full three years. 4.2 was the LTS before 5.2. The download page also states that 6.2 is the last release under that policy; from Django 2028 every feature release gets the same three-year window.

Django support dates. Sources: djangoproject.com/download and endoflife.date, read on 19 November 2026.

SeriesReleasedSecurity support endsLatest releasePython versions
4.2 LTS3 Apr 20237 Apr 2026 (ended)4.2.30, 7 Apr 20263.8 to 3.12
5.04 Dec 20232 Apr 2025 (ended)5.0.14, 2 Apr 20253.10 to 3.12
5.17 Aug 20243 Dec 2025 (ended)5.1.15, 2 Dec 20253.10 to 3.13
5.2 LTS2 Apr 2025April 20285.2.19, 3 Nov 20263.10 to 3.14
6.03 Dec 2025April 20276.0.10, 3 Nov 20263.12 to 3.14
6.15 Aug 2026December 20276.1.3, 3 Nov 20263.12 to 3.15

Python versions per series are from endoflife.date. The Django download page does not list them. Django 5.2 is the last series that runs on Python 3.10 and 3.11, which matters because Python 3.10 reached end of life on 1 October 2026.

Upgrading Django 4.2 to 5.2: what breaks

The upgrade crosses three feature releases, and each one removed code that 4.2 only warned about. Everything below is from the Django 5.0, 5.1 and 5.2 release notes. Python is the first blocker: Django 4.2.x is the last series that supports Python 3.8 and 3.9, and 5.0 requires 3.10 or newer, so a site on Python 3.9 moves the interpreter before it moves Django.

Features removed in 5.1 were deprecated in 4.2, so running 4.2 with deprecation warnings on and clearing them handles most of that list before the jump. The 5.0 changes in the table are different: they change behaviour without warning, and a test suite will not always catch them.

Changes that stop a 4.2 site from starting or change its behaviour. Source: Django 5.0, 5.1 and 5.2 release notes, read on 19 November 2026.

ReleaseChangeWhat it breaks
5.0USE_TZ defaults to True; USE_L10N and pytz support removedSites that relied on naive datetimes must set USE_TZ = False, and any USE_L10N setting is dead
5.0Forms render with a div-based template; the old default.html templates are removedCustom table or paragraph form templates and FORM_RENDERER overrides need a check
5.0LogoutView no longer accepts GETLogout links must become POST forms
5.0Python 3.8 and 3.9 dropped; MySQL 8.0.11 and SQLite 3.27 minimumsInterpreter and database upgrade first
5.1DEFAULT_FILE_STORAGE and STATICFILES_STORAGE removedMove to the STORAGES setting or media and static files stop resolving
5.1SHA1PasswordHasher, UnsaltedSHA1PasswordHasher and UnsaltedMD5PasswordHasher removedUsers whose stored hash uses one of them cannot log in until the hash is upgraded
5.1index_together and the length_is filter removed; PostgreSQL 13 and MariaDB 10.5 minimumsModel Meta and templates need edits; older databases must be upgraded
5.2PostgreSQL 14 minimum; MySQL connections default to utf8mb4A legacy utf8 (utf8mb3) MySQL database needs an explicit charset option
5.2The debug context processor is no longer in the default project templateTemplates that use debug variables must add it back

This is not the full list. The release notes also remove the sessions PickleSerializer, CryptPasswordHasher and the is_dst argument, and change several aggregate and queryset behaviours. Read each release note before you start.

Who patches Django after end of life?

The Django project ships no fixes for an ended series: its security archive lists no 4.2 entry after 7 April 2026, and the advisories published on 6 October and 3 November 2026 name only supported series. Two companies sell fixes for ended Django versions: HeroDevs and OSSeva.

Facts from each provider's own page, read on 19 November 2026.

ProviderDjango versions the page listsFix timing the page states
HeroDevs (NES for Django)Headline names Django 3.2 and 4.2; FAQ names 3.2 as an EOL version; other versions on requestNo numeric CVE timeframe; same-day resolution target where possible; SLA on request
OSSeva4.2, 5.0 and 5.1. Other versions case by caseCritical within 48 hours, High within 7 days

How we compared: HeroDevs' row uses only its own Django page, read on 19 November 2026. The fix-timing column reports what each page states, which are different measures (a target on a page and a patch SLA). Where HeroDevs is the better fit: it lists Django 3.2, which OSSeva does not cover. We did not read other providers' Django pages and have not listed them.

Running an end-of-life Django version?

OSSeva keeps end-of-life Django patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.

Django extended support

Questions

Django end of life: common questions

Book a 15-minute call

Is Django 4.2 end of life?

Yes. Django 4.2 LTS reached end of life on 7 April 2026, and 4.2.30 was its last release. The security advisories the project published on 6 October and 3 November 2026 name only supported series.

When does Django 5.2 LTS reach end of life?

April 2028, per the djangoproject.com download page. Its mainstream support ended on 3 December 2025, so it now receives security fixes only. The latest 5.2 release is 5.2.19 from 3 November 2026.

When does Django 6.0 reach end of life?

April 2027, per the download page. Django 6.1, released on 5 August 2026, is supported until December 2027. Neither 6.0 nor 6.1 is an LTS release.

Is Django 5.0 or 5.1 end of life?

Both. Django 5.0 ended on 2 April 2025 at 5.0.14 and 5.1 ended on 3 December 2025 at 5.1.15, per endoflife.date. OSSeva patches both after end of life.

Which Python versions does Django 4.2 support?

Python 3.8 to 3.12, per endoflife.date. Django 5.0 dropped Python 3.8 and 3.9, so a site on either needs a Python upgrade before it can reach Django 5.x. See Python EOL dates.

Who provides Django support after end of life?

HeroDevs and OSSeva both sell fixes for ended Django versions. OSSeva patches Django 4.2, 5.0 and 5.1 and assesses other versions case by case through a version coverage check.

Is there a Django LTS release?

Yes, for now. 4.2 and 5.2 are LTS releases with extended support. The download page says 6.2 is the last release under that policy, and from Django 2028 every feature release gets the same three-year support period.

What is the latest Django version?

6.1.3, released 3 Nov 2026, on the 6.1 line. Other supported lines: 6.0 and 5.2.

When is the next Django end of life?

Django 6.0 reaches the end of security support on 30 Apr 2027. After that date the project stops shipping security fixes for 6.0, and CVEs disclosed later stay unpatched upstream.

Which Django versions are still supported?

6.1 (until 31 Dec 2027), 6.0 (until 30 Apr 2027) and 5.2 (until 30 Apr 2028). Every other line has reached end of life, per the dates in the table above.

Can I get security patches for an end-of-life Django version?

Yes. OSSeva ships signed builds with backported CVE fixes for Django 5.1 and 5.0 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.

Get a quote

Still running an end-of-life Django?

Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call