Complete end-of-life dates, support windows, and security status for all Xcp Ng versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.4 | 7.4.0 | Mar 31, 2018 | Oct 31, 2018 | 2747 days past EOL | EOL |
| 7.5 | 7.5.0 | Aug 10, 2018 | Jul 25, 2019 | 2480 days past EOL | EOL |
| 7.6 | 7.6.0 | Oct 31, 2018 | Mar 30, 2020 | 2231 days past EOL | EOL |
| 8.0 | 8.0.0 | Jul 25, 2019 | Nov 13, 2020 | 2003 days past EOL | EOL |
| 8.1 | 8.1.0 | Mar 31, 2020 | Mar 31, 2021 | 1865 days past EOL | EOL |
| 8.2 LTS | 8.2.1 | Nov 13, 2020 | Jun 25, 2025 | 318 days past EOL | EOL |
| 8.3 | 8.3.0 | Oct 7, 2024 | Nov 30, 2028 | 936 days remaining | Active |
When a Xcp Ng 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 Xcp Ng 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 →