DJANGO COVERAGE

Django 4.2 LTS is end of life. Your patching does not have to be.

Django extended support from OSSeva keeps Django 4.2 LTS, 5.0 and 5.1 patched after the Django project stopped releasing them: 4.2.30, the last 4.2 release, shipped on 7 April 2026. Critical CVEs are fixed within 48 hours and High within 7 days, priced per application. Other versions are assessed case by case through a version coverage check.

Who it is forTeams running Django 4.2, 5.0 or 5.1 that cannot move to 5.2 or 6.x yet because of Python, a database version or a third-party package
What you getSigned builds with security fixes backported to the Django line you run, and no change to your settings, templates or migrations. Assure adds an upgrade-path assessment.
How it is pricedPer application. Ask for a quote.
What happens nextYou send your work email, we confirm your Django and Python versions, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

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

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Django support dates, read on 19 November 2026

The Django download page lists three supported series. Everything older has ended. Dates for 5.0, 5.1 and 4.2 come from endoflife.date, which matches the project's release notes.

SeriesReleasedSecurity support endsLatest releaseStatus
4.2 LTS3 Apr 20237 Apr 20264.2.30 (7 Apr 2026)End of life
5.04 Dec 20232 Apr 20255.0.14 (2 Apr 2025)End of life
5.17 Aug 20243 Dec 20255.1.15 (2 Dec 2025)End of life
5.2 LTS2 Apr 2025April 20285.2.19 (3 Nov 2026)Supported
6.03 Dec 2025April 20276.0.10 (3 Nov 2026)Supported
6.15 Aug 2026December 20276.1.3 (3 Nov 2026)Supported

Sources: djangoproject.com/download (supported versions) and endoflife.date/api/django.json, read on 19 November 2026.

Django end-of-life dates and upgrade traps →

What blocks a Django 4.2 to 5.2 upgrade

Most 4.2 sites that stay put do so for one of four reasons, each taken from the Django release notes for 5.0, 5.1 and 5.2. The EOL page lists all of them.

  • Python: 5.0 and later need Python 3.10 or newer. 4.2 is the last series on 3.8 and 3.9.
  • Database: 5.1 requires PostgreSQL 13 or newer and 5.2 requires PostgreSQL 14 or newer. 5.0 requires MySQL 8.0.11 and 5.1 requires MariaDB 10.5.
  • Removed settings: DEFAULT_FILE_STORAGE and STATICFILES_STORAGE were removed in 5.1 in favour of STORAGES, and USE_TZ now defaults to True from 5.0.
  • Auth: the SHA1 and unsalted MD5 password hashers were removed in 5.1, and logout over GET stopped working in 5.0.

Full Django 4.2 to 5.2 upgrade checklist →

Why now

Django 4.2 LTS ended on 7 April 2026

The last 4.2 release was 4.2.30 on 7 April 2026. The security advisories Django published on 6 October and 3 November 2026 list fixes only for the supported series (6.1, 6.0 and 5.2, or the first two).

4.2 is pinned to Python 3.8 and 3.9 on many servers

Django 4.2 is the last series that runs on Python 3.8 and 3.9. Django 5.0 and later need Python 3.10, so a Django upgrade can mean a Python upgrade first, and Python 3.9 is itself past end of life.

Django 5.2 LTS runs to April 2028

The djangoproject.com download page lists 5.2 LTS with extended support until April 2028, 6.0 until April 2027 and 6.1 until December 2027. Moving to 5.2 is the usual target; patching is for the sites that cannot move yet.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
4.2 LTS(Community EOL 7 Apr 2026; last release 4.2.30)EOLClean
5.0(Community EOL 2 Apr 2025; last release 5.0.14)EOLClean
5.1(Community EOL 3 Dec 2025; last release 5.1.15)EOLClean
5.2 LTS(Supported by Django until April 2028. Assessed case by case.)CurrentClean
6.0(Supported by Django until April 2027. Assessed case by case.)CurrentClean
6.1(Supported by Django until December 2027. Assessed case by case.)CurrentClean
Django end of life dates for every version →

Running a Django version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for Django 4.2, 5.0 and 5.1 after end of life.

  • Backported security fixes for Django 4.2, 5.0 and 5.1
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and upgrade planning.

  • Everything in Patch
  • SOC 2 / HIPAA attestation package
  • Django upgrade path assessment
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 application and runtime monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Which Django versions does OSSeva patch?

Django 4.2 LTS, 5.0 and 5.1 after end of life. Other versions are assessed case by case through a version coverage check.

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 Django project no longer fixes security issues in it.

How fast are Django vulnerabilities patched?

Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.

How is OSSeva Django support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get Django patched and supported?

Tell us your Django versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

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

Prefer to talk or read more first?

Book a call