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.
Debian 13 is supported until June 30, 2030, its end-of-support date. Active support for Debian 13 ends on August 9, 2028; security fixes continue until that end-of-life date. The next Debian version to reach end of life is 12, on June 30, 2028. 16 of 18 tracked Debian versions are past end of life; the most recent to reach it, 11, did so on August 31, 2026. The full Debian lifecycle, with every version's release and end-of-support date, is in the table below.
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 | — | 10877 days past EOL | EOL |
| 1.2 | 1.2 | Dec 12, 1996 | Oct 23, 1997 | — | 10562 days past EOL | EOL |
| 1.3 | 1.3.1 r.6 | Jul 2, 1997 | Dec 8, 1998 | — | 10151 days past EOL | EOL |
| 2.0 | 2.0r5 | Jul 24, 1998 | Feb 15, 1999 | — | 10082 days past EOL | EOL |
| 2.1 | 2.1r5 | Mar 9, 1999 | Oct 30, 2000 | — | 9459 days past EOL | EOL |
| 2.2 | 2.2r7 | Aug 15, 2000 | Jun 30, 2003 | — | 8486 days past EOL | EOL |
| 3.0 | 3.0r6 | Jul 19, 2002 | Jun 30, 2006 | — | 7390 days past EOL | EOL |
| 3.1 | 3.1r8 | Jun 6, 2005 | Mar 31, 2008 | — | 6750 days past EOL | EOL |
| 4 | 4.0r9 | Apr 8, 2007 | Feb 15, 2010 | — | 6064 days past EOL | EOL |
| 5 | 5.0.10 | Feb 14, 2009 | Feb 6, 2012 | — | 5343 days past EOL | EOL |
| 6 | 6.0.10 | Feb 6, 2011 | Feb 29, 2016 | — | 3859 days past EOL | EOL |
| 7 | 7.11 | May 4, 2013 | May 31, 2018 | Jun 30, 2020 Debian LTS (ended) |
3037 days past EOL | EOL |
| 8 | 8.11 | Apr 25, 2015 | Jun 30, 2020 | Jun 30, 2025 Debian LTS (ended) |
2276 days past EOL | EOL |
| 9 | 9.13 | Jun 17, 2017 | Jun 30, 2022 | Jun 30, 2027 Debian LTS |
1546 days past EOL | EOL |
| 10 | 10.13 | Jul 6, 2019 | Jun 30, 2024 | Jun 30, 2029 Debian LTS |
815 days past EOL | EOL |
| 11 | 11.11 | Aug 14, 2021 | Aug 31, 2026 | Jun 30, 2031 Debian LTS |
23 days past EOL | EOL |
| 12 | 12.15 | Jun 10, 2023 | Jun 30, 2028 | Jun 30, 2033 Debian LTS |
646 days remaining | Active |
| 13 | 13.7 | Aug 9, 2025 | Jun 30, 2030 | Jun 30, 2035 Debian LTS |
1376 days remaining | Active |
[](https://endoflife.ai/debian)
Debian lifecycle status — the real story
Debian's support has three tiers, and the table above shows two of them. The Debian security team supports each stable release for roughly three years (the end of life column). The community Debian LTS project then extends security support to at least five years from release (the extended support column) — for a subset of architectures and packages, and, as the LTS team itself notes, at a level that depends on the sponsorship it receives. Beyond that, Freexian operates a commercial Extended LTS service adding five further years, ten in total.
The practical consequence: a Debian release that has "reached end of life" here is still receiving free security fixes under LTS for about two more years, but only for the packages and architectures the LTS team covers. Verify that your critical packages are inside that set before relying on it.
Verified against the vendor's lifecycle documentation on August 22, 2026.
Debian release and support pattern
Across the 18 release lines with a published release date, Debian has shipped a new line roughly every 1.9 years (median interval). A line typically stays in standard support for about 3.5 years from its release to its standard-support end date.
Of the 18 release lines tracked, 16 are past end of life and 2 are still within support. The newest line, 13, was released August 9, 2025. The next scheduled end of life is 12 on June 30, 2028 — 646 days from this build. The longest-supported line currently published is 13, to June 30, 2030. Upstream also publishes an extended-support phase for 7 lines, shown in the table above.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
Debian security intelligence
CISA KEV history: Debian is named in CISA's Known Exploited Vulnerabilities catalog 1 time, most recently on 2022-03-28. Derived from CISA's live catalog at every build.
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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
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 16 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Debian is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."