Django 6.1 End of Life
Support dates, the patch stream you lose at EOL, and upgrade guidance — rebuilt from live data.
Django 6.1 is actively supported. It reaches end of life on 31 Dec 2027.
Support timeline
Official dates from the Django release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 5 Aug 2026 | — |
| End of life (scheduled) | 31 Dec 2027 | in 509 days |
| Active support ended | 30 Apr 2027 | security fixes only after this |
| Latest release | 6.1 · 5 Aug 2026 | current |
What you lose on 31 Dec 2027
Being supported means fixes keep shipping to this branch. Here is the stream that stops. Source: NVD.
Django CVEs published and patched, by year
31 published in the last 12 months · data refreshed 2026-08-09
At the last-12-month rate of 31 Django CVEs, running 6.1 for a year past 31 Dec 2027 means roughly that many vulnerabilities fixed upstream but never backported to your branch. Past branches bear this out: Django 5.1 has missed 24 since it went end of life.
How much runway a newer branch buys
Django 6.1 is the newest branch — this is the longest runway currently available.
| Branch | End of life | Days left | vs 6.1 |
|---|---|---|---|
| Django 6.1 | 31 Dec 2027 | 509 | this branch |
| Django 6.0 | 30 Apr 2027 | 264 | -245 days |
| Django 5.2 | 30 Apr 2028 | 630 | +121 days |
Review docs.djangoproject.com.
Frequently asked questions
When does Django 6.1 reach end of life?
Django 6.1 reaches end of life on 31 Dec 2027 — 509 days from now. After that date it receives no security fixes.
Is Django 6.1 still supported?
Yes. Django 6.1 is currently maintained. Latest release: 6.1, published 5 Aug 2026.
What happens when Django 6.1 reaches end of life?
Security fixes stop. Over the last 12 months 31 Django vulnerabilities were published and patched across supported branches; once 6.1 is end of life, fixes at that rate no longer reach it.
How long do I have to upgrade from Django 6.1?
509 days. This is already the newest branch, so this is the longest runway currently available.