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: Oct 9, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
10.9 May 13, 2026May 13, 2027May 13, 2028in 568d——Active
10.8.11 Mar 3, 2026Mar 3, 2027Mar 3, 2028in 497d——Active
10.8 Oct 28, 2025Oct 28, 2026Oct 28, 2027in 370d——Active
10.0_u7 May 6, 2025May 6, 2026May 6, 2027in 195d——Active
10.0_u6 Dec 3, 2024Dec 3, 2026Dec 3, 2027in 406d——Active
10.0_u5 Aug 6, 2024Dec 3, 2024Aug 6, 202678d ago——EOL
10.0_u4 May 15, 2024Aug 6, 2024May 15, 2026161d ago——EOL
10.0_u3 Feb 12, 2024May 15, 2024Feb 12, 2026253d ago——EOL
10.0_u2 Nov 28, 2023Feb 12, 2024Dec 31, 2024661d ago——EOL
10.0_u1 Aug 7, 2023Nov 28, 2023Aug 7, 2024807d ago——EOL
10.0 Jul 5, 2023Aug 7, 2023Jul 5, 2024840d ago——EOL
9.7 Nov 8, 2022Dec 31, 2023Dec 31, 2024661d ago——EOL
9.5 Apr 5, 2022May 1, 2023May 1, 2024905d ago——EOL
9.0 Jul 13, 2021Aug 1, 2022Oct 15, 20231104d ago——EOL
8.5 Nov 1, 2020Jan 1, 2022Jan 1, 20231391d ago——EOL
8.0 Mar 22, 2020May 31, 2021Jun 1, 20221605d ago——EOL
7.5 Sep 22, 2019Dec 5, 2020Dec 6, 20211782d ago——EOL
7.0 Apr 26, 2019May 30, 2020May 30, 20211972d ago——EOL
6.5 Sep 16, 2018Oct 30, 2019Oct 30, 20202184d ago——EOL
6.0 Feb 15, 2018Mar 30, 2019Mar 30, 20202398d ago——EOL
5.5 Jul 31, 2017Sep 30, 2018Sep 30, 20192580d ago——EOL
5.0 Nov 8, 2016Aug 31, 2018Aug 31, 20182975d ago——EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions