Proxmox VE 8 End of Life Is August 31, 2026 — 20 Days Out, and It's the First Proxmox Deadline Most VMware Refugees Have Ever Faced
On August 31, 2026 — 20 days from this article's publication — Proxmox VE 8 reaches end of life. Per our tracked lifecycle data, the 8.x line shipped June 22, 2023, closed out at version 8.4 in April 2025, and after August 31 receives no further updates on the 8.x branch — security fixes included. There is no extended-support program to buy, no LTS designation to fall back on, and, unusually for a deadline of this size, almost no independent coverage: people are already searching for "Proxmox VE 8 end of support" and finding mostly forum threads.
The reason this particular EOL deserves more attention than a routine version retirement is who is sitting on PVE 8. After Broadcom's acquisition of VMware closed in late 2023 and VMware's licensing was reworked around subscription bundles, Proxmox VE became one of the most commonly cited destinations for displaced VMware workloads — and Proxmox leaned into the moment: version 8.2 added, in the release notes' own words, an "import wizard for VMware ESXi VMs and templates." The release line that absorbed the VMware exodus is precisely the line that expires in 20 days. For many of those organizations, this is their first Proxmox end of life — and Proxmox's cadence is faster than the multi-year VMware support windows they calibrated their planning on.
pve8to9 checklist tool. There is no Proxmox extended-support tier to defer this with.
What Proxmox's lifecycle policy actually says
Proxmox publishes its support commitment in the Proxmox VE FAQ, and it is worth reading precisely, because it is structured differently from most enterprise lifecycles. Each Proxmox VE version is supported, in the FAQ's words, "at least as long as the corresponding Debian version is supported by the Debian Security Team, i.e. approximately 3 years after its initial release." The FAQ adds: "Proxmox VE uses a rolling release model and using the latest stable version is always recommended." That second sentence is the whole support strategy — there is no extended phase, no paid life-extension, no security-only tail. The FAQ's lifecycle table lists Proxmox VE 8's end of life in August 2026; our tracked data pins it to August 31.
The Debian coupling is not a footnote — it is the mechanism, and it explains why this date is firm. Proxmox VE 8 is built on Debian 12 "Bookworm," and Debian 12 crossed its own line first: per our tracked Debian data, Bookworm left Debian Security Team coverage on July 11, 2026, passing to the LTS team. Proxmox's "at least as long as" commitment has therefore already been fulfilled — August 31 is the "at least" running out. And while Debian 12 LTS continues to June 2028, that covers Debian packages, not the Proxmox-specific kernel and virtualization stack that make a PVE host a hypervisor. Debian LTS keeps a Bookworm system patchable; it does not keep Proxmox VE 8 patched.
One more date for the calendar: August 31, 2026 is a crowded day — Debian 11 Bullseye's LTS window ends the same day. If your estate mixes Proxmox hosts with aging Debian guests, both clocks stop together.
The VMware-refugee wrinkle: a fleet that has never seen a Proxmox EOL
Proxmox VE has existed since 2008, and its long-time operators know the rhythm by feel: a new major roughly every two years, tracking Debian's cadence, with about a year of overlap to move. The history is strikingly consistent — Proxmox VE 7 reached end of life about thirteen months after PVE 8 shipped, and PVE 8 reaches end of life almost exactly thirteen months after PVE 9 shipped on August 5, 2025. The overlap window is the upgrade window, and for PVE 8 it is now 20 days wide.
What changed this cycle is the audience. The organizations that adopted Proxmox VE in 2024 and 2025 — many mid-migration off VMware ESXi after the Broadcom licensing overhaul, a story we covered from the ESXi side — landed on PVE 8 because it was the current release, and in many cases because PVE 8.2's ESXi import wizard was the on-ramp. Those teams calibrated their lifecycle expectations on vSphere, where a major release carried general support measured in many years. Proxmox's model is not that: it is a fast-moving open-source platform whose support window is bounded by Debian's, roughly three years from release, with the project's own FAQ pointing everyone to the latest stable. Neither model is wrong — but planning Proxmox with VMware assumptions means an EOL date arrives before anyone has budgeted an upgrade cycle for it. If your Proxmox estate was born in the VMware exodus, August 31 is the first test of whether its lifecycle tracking came along in the migration.
Every Proxmox VE version's dates
All dates from our tracked lifecycle data, cross-checked against the support lifecycle table in Proxmox's own FAQ. Each version links to its lifecycle page with live status and risk score. Status is as of August 11, 2026.
| Version | Debian base | Released | End of life | Status (as of Aug 11, 2026) |
|---|---|---|---|---|
| Proxmox VE 9 | Debian 13 "Trixie" | Aug 5, 2025 | Not yet announced | Supported — current stable (9.2, May 2026) |
| Proxmox VE 8 | Debian 12 "Bookworm" | Jun 22, 2023 | Aug 31, 2026 | EOL in 20 days |
| Proxmox VE 7 | Debian 11 "Bullseye" | Jul 6, 2021 | Jul 31, 2024 | EOL — unsupported 2+ years |
| Proxmox VE 6 | Debian 10 "Buster" | Jul 16, 2019 | Sep 30, 2022 | EOL |
| Proxmox VE 5 | Debian 9 "Stretch" | Jul 4, 2017 | Jul 31, 2020 | EOL |
| Proxmox VE 4 | Debian 8 "Jessie" | Oct 6, 2015 | Jun 30, 2018 | EOL |
| Proxmox VE 3 | Debian 7 "Wheezy" | May 24, 2013 | Feb 28, 2017 | EOL |
| Proxmox VE 2 | Debian 6 "Squeeze" | Mar 30, 2012 | May 31, 2014 | EOL |
| Proxmox VE 1 | Debian 5 "Lenny" | Sep 13, 2011 | Jan 31, 2013 | EOL |
Release and EOL dates from our tracked dataset (verification pass 2026-08-10), cross-checked against the support lifecycle table in the Proxmox VE FAQ; Debian base versions per the same table. Proxmox VE 9 has no announced end-of-life date — under Proxmox's Debian-coupled policy it is expected to track Debian 13's security-support window, but we list only what is published.
The upgrade path: 8 → 9 is a major, and the OS underneath moves too
The Proxmox VE 8-to-9 upgrade is an in-place major upgrade via apt, documented step by step in Proxmox's official Upgrade from 8 to 9 guide. It is bigger than a point update because it carries the entire base OS from Debian 12 "Bookworm" to Debian 13 "Trixie" in the same operation — kernel, system libraries and the Proxmox stack move together. Proxmox ships a purpose-built preflight tool for exactly this: pve8to9, a checklist program (run it as pve8to9 --full for every check) that inspects each node and reports what needs attention before you start. Per the guide, it only checks and reports — it fixes nothing by itself, which is the correct division of labor for a hypervisor host.
The sequence the guide prescribes, condensed: bring every node to the latest Proxmox VE 8.4 first (pve-manager 8.4.1 or newer — upgrading from an outdated 8.x directly is not the tested path); take tested backups of all VMs and containers; if you run hyper-converged Ceph, upgrade it to Ceph 19.2 "Squid" before the OS upgrade; confirm at least 5-10 GB free on the root filesystem; run pve8to9 --full, resolve its findings, then run the dist-upgrade. Clusters upgrade rolling — one node at a time, live-migrating guests off each node before it upgrades — so a multi-node cluster can cross the major version without guest downtime, but the calendar cost is real: nodes upgrade serially, and 20 days is not a lot of runway for a large cluster that has not started.
One honesty note, because our readers expect it: we checked the live CISA Known Exploited Vulnerabilities catalog on August 10, 2026, and it contains no Proxmox entry. There is no known active exploitation campaign against Proxmox VE to point at — the argument for moving is structural, not incident-driven. Structural is enough: the platform holding every VM is the last place to accumulate unpatchable CVEs, and post-EOL branches accumulate them by definition.
We track Proxmox VE and 480+ other products against vendor-verified dates — every Proxmox VE version with live status, the PVE 8 page with its risk score, check any version in seconds, or see what else hits end of life this quarter.
Proxmox VE currently carries an EOL Risk Score™ of 50/100 — Grade C, elevated risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the Proxmox VE lifecycle page.
The right response comes down to 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 fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination.
Frequently Asked Questions
What happens to Proxmox VE 8 after August 31, 2026?
It leaves Proxmox's support window. Proxmox's published lifecycle commitment is that each Proxmox VE version is supported at least as long as its underlying Debian version is supported by the Debian Security Team, and its lifecycle table lists Proxmox VE 8's end of life in August 2026 — August 31, 2026 in our tracked data. After that date the 8.x branch no longer receives updates through the Proxmox repositories, security fixes included. Hosts keep running, but vulnerabilities disclosed after the date stay unpatched on 8.x permanently.
Is there an extended support or LTS option for Proxmox VE 8?
No. Proxmox publishes one lifecycle per release, with no extended-support tier and no LTS designation — its FAQ states that Proxmox VE uses a rolling release model and using the latest stable version is always recommended. Debian 12, the base of Proxmox VE 8, does continue receiving Debian LTS updates to June 2028, but Debian LTS covers Debian packages only — not the Proxmox-specific kernel, virtualization, storage and cluster packages that make the platform a hypervisor. The supported path is the in-place upgrade to Proxmox VE 9.
How do I upgrade from Proxmox VE 8 to Proxmox VE 9?
It is a major in-place upgrade via apt, documented in Proxmox's official Upgrade from 8 to 9 wiki guide, and it carries the underlying OS from Debian 12 Bookworm to Debian 13 Trixie. The sequence: update every node to the latest Proxmox VE 8.4 (pve-manager 8.4.1 or newer), take tested backups of all VMs and containers, run the pve8to9 checklist tool with its --full flag on every node and resolve what it reports, upgrade hyper-converged Ceph to 19.2 Squid first if you run it, confirm 5-10 GB free on the root filesystem, then perform the dist-upgrade node by node. Clusters upgrade rolling, one node at a time, with guests migrated off each node before it upgrades.
Can I keep running Proxmox VE 8 after its end of life?
It will keep booting and your VMs will keep running — nothing shuts off. What changes is that the hypervisor layer stops receiving security fixes, and a hypervisor is among the highest-value targets in any stack: it holds the disks, memory and network traffic of every guest on the host. For accuracy: as of our check of CISA's Known Exploited Vulnerabilities catalog on August 10, 2026, no Proxmox entry appears in it — the risk argument is exposure without patches, not a known active campaign. If you cannot upgrade by August 31, treat unpatched hosts as legacy infrastructure: restrict access to the management interface, keep hosts off untrusted networks, and schedule the 8-to-9 upgrade as dated work rather than backlog.
Related
- All Proxmox VE versions with live status · Proxmox VE 8 — dates and risk score
- VMware ESXi End of Life — the other side of the migration story: the dates that pushed the exodus
- Debian 11 Has Days of Patches Left — the other August 31, 2026 deadline
- The 2026 EOL Calendar — everything else with an August date