Django 2.x — End of Life
EOLDjango 2.x — All releases
| Version | Released | Active support | EOL date | Latest patch | Status |
|---|---|---|---|---|---|
| 2.2LTS | Apr 1, 2019 | Dec 2, 2019 | Apr 11, 2022 | 2.2.28 | EOL |
| 2.1 | Aug 1, 2018 | Apr 1, 2019 | Dec 2, 2019 | 2.1.15 | EOL |
| 2.0 | Dec 2, 2017 | Aug 1, 2018 | Apr 1, 2019 | 2.0.13 | EOL |
CVEs affecting Django 2.x (0)
Django 2.x is EOL — migrate to Django 3.x
Django 3.x is the next major release. Plan your upgrade before Django 2.x stops receiving security patches.
Frequently asked questions
Is Django 2 end of life?
Yes. All Django 2.x releases have reached end of life and no longer receive security patches. Migrate to Django 3.x as soon as possible.
What CVEs affect Django 2?
No CVEs are currently tracked for Django 2.x in our database. This may mean no vulnerabilities have been recorded yet, or the data is still syncing.
What is the latest Django 2 version?
The latest Django 2.x patch release is 2.2.28, released on April 11, 2022. Always run the latest patch to benefit from all security fixes.
How to migrate from Django 2 to Django 3?
To migrate from Django 2 to Django 3: (1) review the official Django 3 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 2 in production?
No. Django 2 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