Debian 11 EOL: LTS ends on 31 August

Long-term support (LTS) for Debian 11 (“Bullseye”) ends on 31 August 2026. After that, the Debian project will release no more security updates for it. Your servers won’t stop because of this, but every vulnerability found from then on will stay unpatched on them. If you still run Debian 11, you have three weeks to decide before Debian 11 EOL.

How did we get here?

Debian supports each release for about three years through the security team; after that, the LTS team – made up of volunteers and sponsoring companies – provides security fixes for the most important packages and architectures for another two years.

Release Released End of regular support End of LTS
Debian 10 “Buster” July 2019 June 2022 30 June 2024
Debian 11 “Bullseye” 14 August 2021 14 August 2024 31 August 2026
Debian 12 “Bookworm” 10 June 2023 July 2026 30 June 2028
Debian 13 “Trixie” 9 August 2025 expected 2028 expected 30 June 2030

Regular support for Debian 12 ended in July, and since July the security updates come from the LTS team, until 30 June 2028. The current stable release is Debian 13, and its latest point release is 13.6 from July.

What does this mean in practice?

  • No more security fixes. For bugs found in OpenSSH, OpenSSL, the kernel or PHP after 31 August, no updates will come for Debian 11. On a server that is reachable from the internet, this is the biggest risk.
  • Ageing software. Debian 11 ships PHP 7.4, whose upstream support already ended in 2022; until now only the Debian LTS team’s fixes kept it alive. Fewer and fewer newer web applications, plugins and frameworks run on it.
  • External repositories. Third-party package sources (databases, monitoring agents, Docker) are dropping Bullseye one after another, so these won’t be updated any more either.
  • Compliance. If the machine holds personal or payment data, most auditors won’t accept an unsupported operating system.

How do you find the affected machines?

On one machine:

cat /etc/debian_version     # for example 11.11
lsb_release -a              # if installed

If you manage several machines with Ansible, you can query the major version of all of them with a single command (look for the ones with the value "11"):

ansible all -m ansible.builtin.setup -a "filter=ansible_distribution_major_version"

Don’t forget the less visible places either: old virtual machines, LXC containers on a Proxmox server, Docker images built on a debian:bullseye or php:7.4-* base, and appliances on which the vendor shipped Debian 11.

What are your options?

Upgrading to Debian 12, then to 13

For most servers this is the right direction. You can’t skip a release: you have to go from 11 to 12, and then from 12 to 13; the two can’t be combined. Since Debian 12 is already in LTS too, it’s worth going through both steps in one go and leaving the machine on Debian 13.

Over the two release upgrades, the most important components change like this:

Component Debian 11 Debian 12 Debian 13
Linux kernel 5.10 6.1 6.12
PHP 7.4 8.2 8.4
Python 3.9 3.11 3.13
MariaDB 10.5 10.11 11.8
PostgreSQL 13 15 17
OpenSSH 8.4 9.2 10.0

The jump from PHP 7.4 to 8.2 and then 8.4 is the riskiest part: an old web application often doesn’t run on the newer PHP. It’s worth trying this on a test machine before the upgrade.

Extended support (ELTS)

With the paid Extended LTS service from a company called Freexian, you can get security fixes for some Debian 11 packages until 30 June 2031, on a limited set of architectures and packages. It is meant for buying time if a machine can’t be upgraded right now for some reason, not for postponing the upgrade.

Replacement or isolation

If only one or two services run on a machine, it is often simpler to install a fresh Debian 13 and move the data over to it. Where none of this is possible (for example because of an old application that is no longer developed), at least isolate the machine: a separate network segment, no internet access, only the necessary connections, and regular backups.

Upgrading from Debian 11 to 12, step by step

The steps below follow the Debian 12 release notes. Before you start, make a full backup or snapshot, and if you can, work with console access or in a screen/tmux session.

# 1. full update of the current system
apt update && apt full-upgrade
apt autoremove

# 2. switch the repositories to bookworm
sed -i 's/bullseye/bookworm/g' /etc/apt/sources.list /etc/apt/sources.list.d/*.list

# 3. minimal upgrade, then the full one
apt update
apt upgrade --without-new-pkgs
apt full-upgrade

# 4. reboot and check
reboot
cat /etc/debian_version

If the machine has non-free firmware packages, since Debian 12 these are in the separate non-free-firmware component; add it to the lines in sources.list. In Debian 12, the line for the security repository looks like this:

deb http://security.debian.org/debian-security bookworm-security main contrib non-free-firmware

During the upgrade the package manager may ask whether you want to keep modified configuration files. If you aren’t sure, keep your own, and compare it with the .dpkg-dist file afterwards.

Upgrading from Debian 12 to 13

The second step works the same way, with trixie instead of bookworm. Also note the new deb822 format for repository definitions; the apt modernize-sources command converts the old files to it. We also described the steps of a major version upgrade in the knowledge base of our hosting brand, aWh.

Checklist before 31 August

  1. Make an inventory of every Debian 11 machine, container and image.
  2. Prioritise them: which one is reachable from the internet, which one handles sensitive data.
  3. Decide for each machine: upgrade, reinstall, ELTS or isolation.
  4. Test the applications with the new PHP, Python and database versions.
  5. Make a backup, and test the restore too.
  6. Upgrade a test machine first, then the production ones.
  7. After the upgrade, go through the logs (journalctl -p err -b) and the services (systemctl --failed).

We have written about similar situations before: the same steps helped at the time of CentOS 7 EOL and Ubuntu 20.04 EOL. We also help with assessing, upgrading and migrating end-of-life Linux servers; you can read more on our Infrastructure and operations page.

Let’s talk about your project

Tell us briefly how we can help, and we will get back to you as soon as we can.

Get in touch