Complete end-of-life dates, support windows, and security status for all Proxmox Ve versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.9 | Sep 13, 2011 | Jan 31, 2013 | 4846 days past EOL | EOL |
| 2 | 2.3 | Mar 30, 2012 | May 31, 2014 | 4361 days past EOL | EOL |
| 3 | 3.4 | May 24, 2013 | Feb 28, 2017 | 3357 days past EOL | EOL |
| 4 | 4.4 | Oct 6, 2015 | Jun 30, 2018 | 2870 days past EOL | EOL |
| 5 | 5.4 | Jul 4, 2017 | Jul 31, 2020 | 2108 days past EOL | EOL |
| 6 | 6.4 | Jul 16, 2019 | Sep 30, 2022 | 1317 days past EOL | EOL |
| 7 | 7.4 | Jul 6, 2021 | Jul 31, 2024 | 647 days past EOL | EOL |
| 8 | 8.4 | Jun 22, 2023 | Aug 31, 2026 | 114 days remaining | Warning |
| 9 | 9.1 | Aug 5, 2025 | Already EOL | Supported | Active |
When a Proxmox Ve version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Proxmox Ve should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →