Debian End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Debian versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Extended Support | Days | Status |
|---|---|---|---|---|---|---|
| 1.1 | 1.1 | Jun 17, 1996 | Dec 12, 1996 | — | 10832 days past EOL | EOL |
| 1.2 | 1.2 | Dec 12, 1996 | Oct 23, 1997 | — | 10517 days past EOL | EOL |
| 1.3 | 1.3.1 r.6 | Jul 2, 1997 | Dec 8, 1998 | — | 10106 days past EOL | EOL |
| 2.0 | 2.0r5 | Jul 24, 1998 | Feb 15, 1999 | — | 10037 days past EOL | EOL |
| 2.1 | 2.1r5 | Mar 9, 1999 | Sep 30, 2000 | Oct 30, 2000 Debian LTS (ended) |
9444 days past EOL | EOL |
| 2.2 | 2.2r7 | Aug 15, 2000 | Jun 30, 2003 | — | 8441 days past EOL | EOL |
| 3.0 | 3.0r6 | Jul 19, 2002 | Jun 30, 2006 | — | 7345 days past EOL | EOL |
| 3.1 | 3.1r8 | Jun 6, 2005 | Mar 31, 2008 | — | 6705 days past EOL | EOL |
| 4 | 4.0r9 | Apr 8, 2007 | Feb 15, 2010 | — | 6019 days past EOL | EOL |
| 5 | 5.0.10 | Feb 14, 2009 | Feb 6, 2012 | — | 5298 days past EOL | EOL |
| 6 | 6.0.10 | Feb 6, 2011 | May 31, 2014 | Feb 29, 2016 Debian LTS (ended) |
4453 days past EOL | EOL |
| 7 | 7.11 | May 4, 2013 | Apr 25, 2016 | May 31, 2018 Debian LTS (ended) |
3758 days past EOL | EOL |
| 8 | 8.11 | Apr 25, 2015 | Jun 17, 2018 | Jun 30, 2020 Debian LTS (ended) |
2975 days past EOL | EOL |
| 9 | 9.13 | Jun 17, 2017 | Jul 18, 2020 | Jul 1, 2022 Debian LTS (ended) |
2213 days past EOL | EOL |
| 10 | 10.13 | Jul 6, 2019 | Sep 10, 2022 | Jun 30, 2024 Debian LTS (ended) |
1429 days past EOL | EOL |
| 11 | 11.11 | Aug 14, 2021 | Aug 14, 2024 | Aug 31, 2026 Debian LTS |
725 days past EOL | EOL |
| 12 | 12.15 | Jun 10, 2023 | Jul 11, 2026 | Jun 30, 2028 Debian LTS |
29 days past EOL | EOL |
| 13 | 13.6 | Aug 9, 2025 | Aug 9, 2028 | Jun 30, 2030 Debian LTS |
731 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/debian)
What does Debian end of life mean for your organization?
When a version of Debian reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Debian should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Debian reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
For the full decision flow on this product, see our detailed guide: Debian 11: upgrade, ELTS, or commercial support?
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Debian versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Debian has 17 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Debian exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.