Complete end-of-life dates, support windows, and security status for all Zerto versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.0 | — | Nov 8, 2016 | Aug 31, 2018 | 2808 days past EOL | EOL |
| 5.5 | — | Jul 31, 2017 | Sep 30, 2019 | 2413 days past EOL | EOL |
| 6.0 | — | Feb 15, 2018 | Mar 30, 2020 | 2231 days past EOL | EOL |
| 6.5 | — | Sep 16, 2018 | Oct 30, 2020 | 2017 days past EOL | EOL |
| 7.0 | — | Apr 26, 2019 | May 30, 2021 | 1805 days past EOL | EOL |
| 7.5 | — | Sep 22, 2019 | Dec 6, 2021 | 1615 days past EOL | EOL |
| 8.0 | — | Mar 22, 2020 | Jun 1, 2022 | 1438 days past EOL | EOL |
| 8.5 | — | Nov 1, 2020 | Jan 1, 2023 | 1224 days past EOL | EOL |
| 9.0 | — | Jul 13, 2021 | Oct 15, 2023 | 937 days past EOL | EOL |
| 9.5 | — | Apr 5, 2022 | May 1, 2024 | 738 days past EOL | EOL |
| 9.7 | — | Nov 8, 2022 | Dec 31, 2024 | 494 days past EOL | EOL |
| 10.0 | — | Jul 5, 2023 | Aug 7, 2023 | 1006 days past EOL | EOL |
| 10.0_u1 | — | Aug 7, 2023 | Nov 28, 2023 | 893 days past EOL | EOL |
| 10.0_u2 | — | Nov 28, 2023 | Feb 12, 2024 | 817 days past EOL | EOL |
| 10.0_u3 | — | Feb 12, 2024 | May 15, 2024 | 724 days past EOL | EOL |
| 10.0_u4 | — | May 15, 2024 | Aug 6, 2024 | 641 days past EOL | EOL |
| 10.0_u5 | — | Aug 6, 2024 | Dec 3, 2024 | 522 days past EOL | EOL |
| 10.0_u6 | — | Dec 3, 2024 | Dec 3, 2026 | 208 days remaining | Active |
| 10.0_u7 | — | May 6, 2025 | May 6, 2026 | 3 days past EOL | EOL |
| 10.8 | — | Oct 28, 2025 | Oct 28, 2026 | 172 days remaining | Warning |
When a Zerto 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 Zerto 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 →