{"id":18619,"date":"2026-09-01T11:23:57","date_gmt":"2026-09-01T18:23:57","guid":{"rendered":"https:\/\/jasonsblog.ddns.net\/?p=18619"},"modified":"2026-09-01T11:23:57","modified_gmt":"2026-09-01T18:23:57","slug":"debian-11-bullseye-is-now-officially-unsupported","status":"publish","type":"post","link":"https:\/\/jasonsblog.ddns.net\/index.php\/2026\/09\/01\/debian-11-bullseye-is-now-officially-unsupported\/","title":{"rendered":"Debian 11 \u201cBullseye\u201d Is Now Officially Unsupported"},"content":{"rendered":"\n

(Headline blog post below) I\u2019ve always been aware of the Debian LTS and the ELTS project<\/a> run by Freexian<\/a>, and when my Raspberry PI PBX on buster went off LTS I tried it since I haven’t replaced that Raspberry Pi 3B yet. I don’t allow it to take incoming connections with just outbound trunks to my VOIP provider, so I’m not too worried about the old Asterisk and FreePBX software. And it regularly pulls in security fixes for OS packages from Freexian. So if you have a Bullseye project you want to continue using, you can switch to Freexian’s ELTS support which I’ve just done with my DVSwitch server which is a Raspberry Pi 3B+ with AMBE hardware vocoder. So you don’t have to upgrade the OS unless your threat model requires it.<\/p>\n\n\n\n

\"\"<\/a><\/figure>\n\n\n\n

https:\/\/linuxiac.com\/debian-11-bullseye-is-now-officially-unsupported\/<\/a><\/p>\n\n\n

<\/div><\/div><\/div>\n\n\n
Debian 11 \u201cBullseye\u201d reaches end of life on August 31, 2026, after five years of official support.<\/h5>\n\n\n\n

By Bobby Borisov<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Debian 11 \u201cBullseye\u201d<\/a> has officially reached the end of its life today, August 31, 2026<\/a>, bringing its five-year support cycle to a close. Starting in September, the Debian Project will no longer provide security updates for the release.<\/p>\n\n\n\n

Originally released on August 14, 2021, Bullseye received three years of regular Debian support. On August 14, 2024, the Debian Long Term Support team took over responsibility<\/a> for security updates, extending its usable life for another two years.<\/p>\n\n\n\n

That LTS period ends today. In other words, Debian 11 is now fully outside Debian\u2019s official support lifecycle, and systems still running it should be upgraded to a supported release.<\/p>\n\n\n\n

\"Debian<\/a>
Debian 11 \u201cBullseye\u201d<\/figcaption><\/figure>\n\n\n\n

The Debian team recommends moving first to Debian 12 \u201cBookworm,\u201d which is currently covered by LTS until June 30, 2028. From there, users can later upgrade to Debian 13 \u201cTrixie\u201d<\/a> when appropriate.<\/p>\n\n\n\n

During its LTS phase, Bullseye security coverage was already limited to four architectures: amd64, i386, arm64, and armhf.<\/p>\n\n\n\n

Debian 11\u2019s final point release was Debian 11.11, published on August 31, 2024. It was explicitly announced by the project as the eleventh and final update in the Bullseye point-release series, bundling security fixes and corrections for serious issues accumulated up to that point.<\/p>\n\n\n\n

For users unable to migrate immediately, there is one additional option. A subset of Bullseye packages can continue receiving security coverage through Extended LTS services provided by external parties. However, this should not be confused with regular Debian or Debian LTS support. The Debian Project itself will stop issuing Bullseye security updates starting in September.<\/p>\n\n\n\n

So, if you still have Debian 11 running on a server, workstation, or other production system, now is the time to plan its replacement. After five years, Bullseye\u2019s official journey has come to an end.<\/p>\n","protected":false},"excerpt":{"rendered":"

(Headline blog post below) I\u2019ve always been aware of the Debian LTS and the ELTS project run by Freexian, and when my Raspberry PI PBX on buster went off LTS I tried it since I haven’t replaced that Raspberry Pi 3B yet. I don’t allow it to take incoming connections with just outbound trunks to […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[6],"tags":[],"class_list":["post-18619","post","type-post","status-publish","format-standard","hentry","category-tech"],"blocksy_meta":{"styles_descriptor":{"styles":{"desktop":"","tablet":"","mobile":""},"google_fonts":[],"version":7}},"featured_image_src":null,"author_info":{"display_name":"Jason","author_link":"https:\/\/jasonsblog.ddns.net\/index.php\/author\/jturning\/"},"_links":{"self":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/18619","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/comments?post=18619"}],"version-history":[{"count":1,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/18619\/revisions"}],"predecessor-version":[{"id":18622,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/posts\/18619\/revisions\/18622"}],"wp:attachment":[{"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/media?parent=18619"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/categories?post=18619"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jasonsblog.ddns.net\/index.php\/wp-json\/wp\/v2\/tags?post=18619"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}