Zerto End of Life Dates
other
Disaster recovery, ransomware resilience, and workload mobility are essential considerations for developers working with virtualized infrastructures and cloud environments. Zerto, a subsidiary of Hewlett Packard Enterprise, addresses these concerns with its software solutions, providing a robust framework for ensuring business continuity and data protection. Since its inception, Zerto has been maintained by Hewlett Packard Enterprise, a renowned company headquartered in Spring, Texas, USA, and has become a trusted tool for developers seeking to safeguard their applications and data.
The end-of-life landscape for Zerto is characterized by a total of 22 versions, with 16 of these versions having already reached their end-of-life. Currently, 6 versions remain active, although no latest stable version has been specified. Developers should be aware that version 10.0_u5 is slated to expire on 2026-08-06, marking the next significant milestone in the Zerto lifecycle. This follows the recent end-of-life date of 2026-05-15 for version 10.0_u4, highlighting the need for developers to stay informed about the evolving landscape of Zerto versions and plan their upgrades accordingly.
Given the absence of tracked CVEs, with a total count of 0 and no critical CVEs, the security picture for Zerto appears to be relatively stable. Without a most affected version, developers can focus on maintaining their existing Zerto deployments and planning for future upgrades. Since there are no known vulnerabilities, the KEV status is not applicable in this case. To ensure continued support and security, developers should prioritize monitoring the Zerto version lifecycle and take proactive steps to upgrade to supported versions before the next EOL date, thereby minimizing potential risks and maintaining the resilience of their applications and data.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 10.9 | May 13, 2026 | May 13, 2027 | May 13, 2028 | in 614d | — | — | Active | |
| 10.8.11 | Mar 3, 2026 | Mar 3, 2027 | Mar 3, 2028 | in 543d | — | — | Active | |
| 10.8 | Oct 28, 2025 | Oct 28, 2026 | Oct 28, 2027 | in 416d | — | — | Active | |
| 10.0_u7 | May 6, 2025 | May 6, 2026 | May 6, 2027 | in 241d | — | — | Active | |
| 10.0_u6 | Dec 3, 2024 | Dec 3, 2026 | Dec 3, 2027 | in 452d | — | — | Active | |
| 10.0_u5 | Aug 6, 2024 | Dec 3, 2024 | Aug 6, 2026 | 32d ago | — | — | EOL | |
| 10.0_u4 | May 15, 2024 | Aug 6, 2024 | May 15, 2026 | 115d ago | — | — | EOL | |
| 10.0_u3 | Feb 12, 2024 | May 15, 2024 | Feb 12, 2026 | 207d ago | — | — | EOL | |
| 10.0_u2 | Nov 28, 2023 | Feb 12, 2024 | Dec 31, 2024 | 615d ago | — | — | EOL | |
| 10.0_u1 | Aug 7, 2023 | Nov 28, 2023 | Aug 7, 2024 | 761d ago | — | — | EOL | |
| 10.0 | Jul 5, 2023 | Aug 7, 2023 | Jul 5, 2024 | 794d ago | — | — | EOL | |
| 9.7 | Nov 8, 2022 | Dec 31, 2023 | Dec 31, 2024 | 615d ago | — | — | EOL | |
| 9.5 | Apr 5, 2022 | May 1, 2023 | May 1, 2024 | 859d ago | — | — | EOL | |
| 9.0 | Jul 13, 2021 | Aug 1, 2022 | Oct 15, 2023 | 1058d ago | — | — | EOL | |
| 8.5 | Nov 1, 2020 | Jan 1, 2022 | Jan 1, 2023 | 1345d ago | — | — | EOL | |
| 8.0 | Mar 22, 2020 | May 31, 2021 | Jun 1, 2022 | 1559d ago | — | — | EOL | |
| 7.5 | Sep 22, 2019 | Dec 5, 2020 | Dec 6, 2021 | 1736d ago | — | — | EOL | |
| 7.0 | Apr 26, 2019 | May 30, 2020 | May 30, 2021 | 1926d ago | — | — | EOL | |
| 6.5 | Sep 16, 2018 | Oct 30, 2019 | Oct 30, 2020 | 2138d ago | — | — | EOL | |
| 6.0 | Feb 15, 2018 | Mar 30, 2019 | Mar 30, 2020 | 2352d ago | — | — | EOL | |
| 5.5 | Jul 31, 2017 | Sep 30, 2018 | Sep 30, 2019 | 2534d ago | — | — | EOL | |
| 5.0 | Nov 8, 2016 | Aug 31, 2018 | Aug 31, 2018 | 2929d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
