Django 3.x — End of Life
EOL High riskDjango 3.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status | Alert me |
|---|---|---|---|---|---|---|
| 3.2LTS | Apr 6, 2021 | Dec 7, 2021 | Apr 1, 2024 | 3.2.25 | EOL | |
| 3.1 | Aug 4, 2020 | Apr 6, 2021 | Dec 7, 2021 | 3.1.14 | EOL | |
| 3.0 | Dec 2, 2019 | Aug 3, 2020 | Apr 6, 2021 | 3.0.14 | EOL |
CVEs affecting Django 3.x (9)
| CVE | Severity | CVSS | EPSS | KEV | Cycle | Description | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-15830 | MEDIUM | 5.3 | 1.25% | — | 3.1 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeome… | Aug 4, 2026 |
| CVE-2026-15830 | MEDIUM | 5.3 | 1.25% | — | 3.0 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeome… | Aug 4, 2026 |
| CVE-2026-15830 | MEDIUM | 5.3 | 1.25% | — | 3.2 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango's `django.contrib.gis.geos.GEOSGeome… | Aug 4, 2026 |
| CVE-2026-15337 | MEDIUM | 5.3 | 1.02% | — | 3.1 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()… | Aug 4, 2026 |
| CVE-2026-15337 | MEDIUM | 5.3 | 1.02% | — | 3.0 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()… | Aug 4, 2026 |
| CVE-2026-15337 | MEDIUM | 5.3 | 1.02% | — | 3.2 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. `django.utils.translation.check_for_language()… | Aug 4, 2026 |
| CVE-2026-15307 | HIGH | 8.8 | 0.89% | — | 3.0 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse… | Aug 4, 2026 |
| CVE-2026-15307 | HIGH | 8.8 | 0.89% | — | 3.2 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse… | Aug 4, 2026 |
| CVE-2026-15307 | HIGH | 8.8 | 0.89% | — | 3.1 | An issue was discovered in Django 5.2 before 5.2.17 and 6.0 before 6.0.8. GeoDjango spatial lookups optimistically parse… | Aug 4, 2026 |
Django 3.x is EOL — migrate to Django 4.x
Django 4.x is the next major release. Plan your upgrade before Django 3.x stops receiving security patches.
Frequently asked questions
Is Django 3 end of life?
Yes. All Django 3.x releases have reached end of life and no longer receive security patches. There are 9 known CVEs affecting Django 3.x. Migrate to Django 4.x as soon as possible.
What CVEs affect Django 3?
There are 9 CVEs tracked for Django 3.x. See the full list above with CVSS and EPSS scores.
What is the latest Django 3 version?
The latest Django 3.x patch release is 3.2.25, released on March 4, 2024. Always run the latest patch to benefit from all security fixes.
How to migrate from Django 3 to Django 4?
To migrate from Django 3 to Django 4: (1) review the official Django 4 migration guide for breaking changes, (2) update dependencies and configuration accordingly, (3) test thoroughly in a staging environment, (4) deploy with a rollback plan. Starting early gives you time to resolve compatibility issues before your current version reaches end of life.
Is it safe to run Django 3 in production?
No. Django 3 has reached end of life and security vulnerabilities are no longer patched. Upgrade to a supported version immediately.
Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA