Debian 12 Is EOL as of Today (July 12, 2026) — Your Actual Situation

Today — July 12, 2026 — Debian 12 "Bookworm" reaches the end of its regular security support. The Debian security team has shipped its final advisories for Bookworm; from today, responsibility shifts, coverage narrows, and the clock that matters to your compliance auditor has formally run out. If you run Debian 12 in production, here is precisely what changed overnight, what didn't, and the three paths forward.

Key Dates at a Glance

Debian 13 (Trixie): regular support ends 2028-08-09; LTS ends 2030-06-30
Debian 12 (Bookworm): regular support ends 2026-07-12; LTS ends 2028-06-30
Debian 11 (Bullseye): regular support ends 2024-08-14; LTS ends 2026-08-31
Debian 10 (Buster): regular support ends 2022-09-10; LTS ends 2024-06-30
Debian 9 (Stretch): regular support ends 2020-07-18; LTS ends 2022-07-01
Debian 5 (Lenny): regular support ends 2012-02-06

What actually stops today

Debian's model gives each release roughly three years of full support from the security team. Bookworm shipped on June 10, 2023, and that window closes today. Specifically:

Debian security team advisories (DSAs) for Bookworm end. The full-coverage, all-architectures, all-packages security guarantee is over.
Point releases end. No further 12.x updates roll up fixes.
The compliance answer changes. "Is this OS vendor-supported?" now requires an asterisk — and frameworks like PCI DSS don't love asterisks.

Running Debian 12 past end of life?

Extended support past the official EOL date exists for many products in this position — whether it covers Debian 12 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.” Free, no obligation.

What doesn't stop (and where the trap hides)

Debian is gentler than most: Bookworm now enters Debian LTS, where a separate volunteer/funded team continues security fixes until roughly June 2028 — but only for a subset of architectures and packages. The trap is in that subset: LTS coverage is narrower than full support, exclusions are published package-by-package, and if something you depend on falls outside it, you're unpatched without noticing. Treat LTS as a managed bridge, not a continuation of the status quo — and verify your critical packages are actually covered.

The double deadline

If you're still on Debian 11 "Bullseye," its LTS window closes on August 31, 2026. Organizations that deferred the 11→12 upgrade are about to be two releases behind with no free support at all. That migration is now urgent, not deferred.

Your three paths, honestly ranked

1. Upgrade to Debian 13 "Trixie" (the default answer). Trixie shipped August 9, 2025 — it's had nearly a year of stabilization, and the in-place apt upgrade path from 12 is well-documented and generally uneventful for standard workloads. It resets your clock for years. Most teams should simply schedule this.

2. Ride Debian LTS deliberately. Legitimate when you have Bookworm-pinned dependencies that can't move yet — but do it as a decision, not a drift: confirm your architecture and critical packages are in LTS coverage, put the June 2028 end date in your roadmap, and document the residual risk.

3. Commercial extended support. If you're stuck on 12 (or still on 11) with compliance requirements the community LTS subset can't satisfy, commercial vendors provide fuller extended coverage. Tell us what you're running and we'll match you with a vetted provider — free, within one business day.

The wider week this lands in

Bookworm's EOL headlines an unusually brutal stretch of the EOL calendar: June 30 alone retired Spring Boot 3.5, Spring Framework 6.2, Amazon Linux 2, Kubernetes 1.33's upstream line, and MariaDB 10.6 followed on July 6. On July 14, 2026, SharePoint 2016 and 2019 both exited support on the same day. If your patch dashboard looks quiet, it isn't because nothing happened.

Check any product's real status in seconds with the EOL Checker — it regenerates from live lifecycle data at every build — or see the full Debian release timeline for every version's dates. And if today's news is your problem: the complete Debian 12 action guide covers upgrade paths and pitfalls in depth.

Frequently Asked Questions

Is Debian 12 still supported?

Not by the Debian security team. Debian 12 “Bookworm”’s regular security support ended 2026-07-12. It is now in Debian LTS, which continues security fixes for a subset of packages and architectures until 2028-06-30. Whether your system is covered depends on whether every package you rely on is inside that subset.

What is the difference between Debian regular support and Debian LTS?

Regular support is the Debian security team’s full guarantee: all packages, all architectures, DSAs and point releases, for roughly three years after release. LTS is a separate volunteer-and-sponsor effort that extends security fixes for about two more years — but only for the main packages and a reduced architecture list, with exclusions published package by package. Bookworm’s LTS runs to 2028-06-30.

Should I upgrade Debian 12 to Debian 13?

For most systems, yes. Debian 13 “Trixie” was released 2025-08-09, its regular support runs to 2028-08-09 and its LTS to 2030-06-30, and the in-place apt upgrade from 12 is well documented. Staying on 12 under LTS is defensible only as an explicit decision with the 2028 end date on the roadmap.

Is Debian 11 still supported?

Only until 2026-08-31, when Debian 11 “Bullseye”’s LTS window closes. After that there are no free security fixes for Bullseye at all, and a system still on 11 is two releases behind. That upgrade is urgent.

Is there commercial extended support for Debian 12?

Yes. Beyond community LTS, Extended LTS and commercial extended-support offerings cover Debian releases past their free windows — useful when compliance requires fuller coverage than the LTS subset provides, or for Debian 11 once its LTS ends. Tell us what you run via the form on this page and we will match you with a vetted option — free, within one business day.