Complete end-of-life dates, support windows, and security status for all Ovirt versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 3.6 | 3.6.13.5 | Sep 25, 2015 | Jun 23, 2016 | 3607 days past EOL | EOL |
| 4.0 | 4.0.7.5 | May 31, 2016 | Jan 12, 2017 | 3404 days past EOL | EOL |
| 4.1 | 4.1.11.2 | Jan 12, 2017 | Dec 17, 2017 | 3065 days past EOL | EOL |
| 4.2 | 4.2.8.9 | Dec 4, 2017 | Feb 4, 2019 | 2651 days past EOL | EOL |
| 4.3 | 4.3.11.4 | Jan 22, 2019 | May 20, 2020 | 2180 days past EOL | EOL |
| 4.4 | 4.4.10.7 | May 6, 2020 | May 20, 2022 | 1450 days past EOL | EOL |
| 4.5 | 4.5.7 | Mar 16, 2022 | Already EOL | Supported | Active |
When a Ovirt 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 Ovirt 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 →