Django 1.x — End of Life
EOL High riskDjango 1.x reached end of life on Apr 1, 2020, 2380 days ago, and no longer receives security fixes. The most recent release in this series is 1.11.29. 3 CVEs are tracked for this series. 3 of them were published after the end of life of the affected cycle and will not get an official patch. The next major version is Django 2. See Django 2 →
Django 1.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status | Alert me |
|---|---|---|---|---|---|---|
| 1.11LTS | Apr 4, 2017 | Dec 2, 2017 | Apr 1, 2020 | 1.11.29 | EOL | |
| 1.10 | Aug 1, 2016 | Apr 4, 2017 | Dec 2, 2017 | 1.10.8 | EOL | |
| 1.9 | Dec 1, 2015 | Aug 1, 2016 | Apr 4, 2017 | 1.9.13 | EOL | |
| 1.8 | Apr 1, 2015 | Dec 1, 2015 | Apr 1, 2018 | 1.8.19 | EOL | |
| 1.7 | Sep 3, 2014 | Apr 1, 2015 | Dec 1, 2015 | 1.7.11 | EOL | |
| 1.6 | Nov 6, 2013 | Sep 2, 2014 | Apr 1, 2015 | 1.6.11 | EOL | |
| 1.5 | Feb 26, 2013 | Nov 6, 2013 | Sep 2, 2014 | 1.5.12 | EOL | |
| 1.4 | Mar 23, 2012 | Feb 26, 2013 | Oct 1, 2015 | 1.4.22 | EOL | |
| 1.3 | Mar 23, 2011 | Mar 23, 2012 | Feb 26, 2013 | 1.3.7 | EOL |
CVEs affecting Django 1.x (27)
| CVE | Severity | CVSS | EPSS | KEV | Cycle | Description | Published |
|---|---|---|---|---|---|---|---|
| CVE-2026-15830 | MEDIUM | 5.3 | 0.76% | — | 1.6 | 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 | 0.76% | — | 1.7 | 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 | 0.76% | — | 1.9 | 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 | 0.76% | — | 1.8 | 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 | 0.76% | — | 1.3 | 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 | 0.76% | — | 1.11 | 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 | 0.76% | — | 1.10 | 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 | 0.76% | — | 1.5 | 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 | 0.76% | — | 1.4 | 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 | 0.59% | — | 1.8 | 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 | 0.59% | — | 1.3 | 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 | 0.59% | — | 1.5 | 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 | 0.59% | — | 1.10 | 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 | 0.59% | — | 1.6 | 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 | 0.59% | — | 1.9 | 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 | 0.59% | — | 1.4 | 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 | 0.59% | — | 1.11 | 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 | 0.59% | — | 1.7 | 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 | 1.09% | — | 1.10 | 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 | 1.09% | — | 1.3 | 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 | 1.09% | — | 1.4 | 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 | 1.09% | — | 1.5 | 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 | 1.09% | — | 1.7 | 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 | 1.09% | — | 1.8 | 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 | 1.09% | — | 1.6 | 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 | 1.09% | — | 1.11 | 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 | 1.09% | — | 1.9 | 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 1.x is EOL — migrate to Django 2.x
Django 2.x is the next major release. Plan your upgrade before Django 1.x stops receiving security patches.
Add a Django 1 EOL badge to your README
Show your users which Django version your project runs and whether it is still supported. The badge updates automatically. More formats and options →
[](https://eolcanary.com/explore/django/1)Frequently asked questions
Is Django 1 end of life?
Yes. All Django 1.x releases have reached end of life and no longer receive security patches. There are 3 known CVEs affecting Django 1.x. Migrate to Django 2.x as soon as possible.
What CVEs affect Django 1?
There are 3 CVEs tracked for Django 1.x. See the full list above with CVSS and EPSS scores.
What is the latest Django 1 version?
The latest Django 1.x patch release is 1.11.29, released on March 4, 2020. Always run the latest patch to benefit from all security fixes.
How to migrate from Django 1 to Django 2?
To migrate from Django 1 to Django 2: (1) review the official Django 2 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 1 in production?
No. Django 1 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