Debian Releases, EOL Dates & Version History

Version Timeline

All tracked releases with lifecycle status and EOL dates.

Loading version data…

Lifecycle Timeline

Visual overview of active support and maintenance windows.

10 Buster

11 Bullseye

12 Bookworm

13 Trixie

2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032

Active

Maint

Active

Maint

Active

Maint

Active

Maint

Active / LTS

Maintenance

Today

Upgrade Paths

Migration guidance between major versions — breaking changes, effort estimates, and tips.

11 Bullseye 12 Bookworm Medium Difficulty

Est. 1-2 hours per server

Breaking Changes

Kernel 6.1 (from 5.10)
Python 3.11 replaces 3.9
OpenSSL 3.0 replaces 1.1.1
PHP 8.2 replaces 7.4
non-free-firmware split from non-free
Merged /usr by default
rsyslog replaced by systemd-journald as default

Migration Notes

The OpenSSL change is the biggest server-side impact (same as Ubuntu 22.04). Update sources.list to bookworm, apt update, apt full-upgrade. The non-free-firmware split means you may need to update your sources.list to include non-free-firmware separately. Read the Debian 12 release notes for full details.

10 Buster 12 Bookworm High Difficulty

Est. 3-6 hours (two sequential upgrades)

Breaking Changes

Must upgrade through 11 first (cannot skip)
All breaking changes from 10→11 and 11→12 combined
Two kernel major version jumps
Two Python major version changes

Migration Notes

Upgrade in sequence: Buster → Bullseye → Bookworm. Each hop takes 1-2 hours. Budget a full day for the process including testing. If the system is critical, consider a fresh install with configuration migration instead.

Version Risk Assessment

Evaluate risk factors before choosing a version for production.

Version	EOL Risk	CVE Risk	Ecosystem	Cloud Support	Overall	Recommended Action
Debian 9 Stretch and older	Critical	Critical	Dead	None	Critical	Years past EOL — rebuild on current
Debian 10 Buster	Critical	High	ELTS only	None	Critical	LTS ended Jun 2024 — upgrade immediately
Debian 11 Bullseye	Medium	Low	LTS	Full	Medium	LTS until Jun 2026 — plan upgrade to 12
Debian 12 Bookworm	None	Low	Active	Full	Low	Current stable — recommended

Debian stable gets 3 years of official security support + 2 years LTS. Running unsupported versions means no kernel or package security patches. Assessed March 2026.

Debian Release Feature Comparison

Side-by-side feature differences across major versions.

Feature	10 Buster	11 Bullseye	12 Bookworm
Kernel	4.19	5.10	6.1
Python	3.7	3.9	3.11
OpenSSL	1.1.1	1.1.1	3.0
GCC	8	10	12
systemd	241	247	252
PHP	7.3	7.4	8.2
PostgreSQL	11	13	15
Merged /usr	Optional	Optional	Default
nftables	Default	Default	Default
Security support	Ended	LTS to Jun 2026	Full to Jun 2026

Embed Badges

Add live Debian status badges to your README, docs, or dashboard.

Health Status

Overall support health

![Debian Health Status](https://img.releaserun.com/badge/health/debian.svg)

EOL Countdown

Next end-of-life date

![Debian EOL Countdown](https://img.releaserun.com/badge/eol/debian.svg)

Latest Version

Current stable release

![Debian Latest Version](https://img.releaserun.com/badge/v/debian.svg)

CVE Status

Known vulnerabilities

![Debian CVE Status](https://img.releaserun.com/badge/cve/debian.svg)

Frequently Asked Questions

Common questions about Debian releases and lifecycle.

How long is each Debian release supported?

Each Debian stable release gets approximately 3 years of full support from the Debian Security Team, then 2 additional years of LTS support from the Debian LTS team (5 years total). Extended LTS (ELTS, commercial) can add another 5 years. Debian 12 (Bookworm) was released June 2023 and will be supported until approximately June 2028.

What is the difference between stable, testing, and unstable?

Stable (currently Bookworm/12) is the production release with security patches. Testing (Trixie/13) gets packages that have been in unstable for 5+ days without release-critical bugs. Unstable (Sid) gets new uploads directly. Use stable for servers, testing for desktop/development, and unstable only if you want to contribute or need bleeding-edge packages. Never use testing or unstable on production servers.

What are Debian backports?

Backports are newer package versions rebuilt for the current stable release. They are official (from backports.debian.org) and tested for compatibility with stable. Use backports when you need a newer version of a specific package (e.g., newer kernel, newer PostgreSQL) without upgrading the entire OS. Add the backports repository and install with apt -t bookworm-backports install package.

Which Debian version should I use for Docker containers?

debian:bookworm-slim is the recommended base image. It is ~28MB compressed, smaller than ubuntu, and has the same package manager (apt). The -slim variant removes documentation and unnecessary files. For even smaller images, use Alpine. For compatibility with Ubuntu-based toolchains, debian:bookworm (full) works well. Many official Docker images (Python, Node, Ruby) already use Debian as their base.

How do I upgrade between Debian major versions?

Update /etc/apt/sources.list to point to the new release codename (e.g., bullseye → bookworm), then run apt update && apt full-upgrade. Debian supports upgrading from N to N+1 only (you cannot skip versions). Read the release notes before upgrading: they list known issues and required manual steps. The upgrade takes 30-60 minutes and requires a reboot.

Debian vs Ubuntu: when to choose Debian?

Choose Debian when you want: pure open-source with no commercial agenda, minimal default installation, maximum stability (packages are older but rock-solid), or a universal base for custom systems. Choose Ubuntu when you want: newer packages in LTS, commercial support (Canonical), better cloud tooling integration, or PPAs for third-party software. For Docker base images, Debian slim is often the better choice.

Related Tools

Dep EOL Scanner

Check your dependencies for end-of-life packages.

Stack Health Scorecard

Get an overall health grade for your tech stack.

Release Index

Browse all tracked platforms and their release timelines.