Django 5.2 · Version Status
Django 5.2 End of Life Date
Django 5.2 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Django 5.2 is actively supported. EOL date: April 30, 2028.
EOL Date
Apr 30, 2028
722 days remaining
Latest Release
5.2.14
LTS release
Release Date
Apr 2, 2025
Django 5.2 series
| Version | Latest | EOL Date | Status |
|---|
| 1.3 |
1.3.7 |
Feb 26, 2013 |
EOL |
| 1.4 |
1.4.22 |
Oct 1, 2015 |
EOL |
| 1.5 |
1.5.12 |
Sep 2, 2014 |
EOL |
| 1.6 |
1.6.11 |
Apr 1, 2015 |
EOL |
| 1.7 |
1.7.11 |
Dec 1, 2015 |
EOL |
| 1.8 |
1.8.19 |
Apr 1, 2018 |
EOL |
| 1.9 |
1.9.13 |
Apr 4, 2017 |
EOL |
| 1.10 |
1.10.8 |
Dec 2, 2017 |
EOL |
What does Django 5.2 end of life mean?
When Django 5.2 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Django 5.2 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Django 6.0 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Django 5.2 reach end of life?
Django 5.2 reached end of life on April 30, 2028. That is 722 days remaining.
Is Django 5.2 still supported?
Yes, Django 5.2 is currently supported. The EOL date is April 30, 2028.
What should I upgrade to from Django 5.2?
The recommended upgrade from Django 5.2 is
Django 6.0 — the latest actively supported version. Check the
Django full timeline for all supported versions.
What are the security risks of running Django 5.2 past EOL?
When Django 5.2 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Django should migrate immediately or implement compensating controls.