Zerto End of Life (EOL) Dates & Support Timeline
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 | 2871 days past EOL | EOL |
| 5.5 | — | Jul 31, 2017 | Sep 30, 2019 | 2476 days past EOL | EOL |
| 6.0 | — | Feb 15, 2018 | Mar 30, 2020 | 2294 days past EOL | EOL |
| 6.5 | — | Sep 16, 2018 | Oct 30, 2020 | 2080 days past EOL | EOL |
| 7.0 | — | Apr 26, 2019 | May 30, 2021 | 1868 days past EOL | EOL |
| 7.5 | — | Sep 22, 2019 | Dec 6, 2021 | 1678 days past EOL | EOL |
| 8.0 | — | Mar 22, 2020 | Jun 1, 2022 | 1501 days past EOL | EOL |
| 8.5 | — | Nov 1, 2020 | Jan 1, 2023 | 1287 days past EOL | EOL |
| 9.0 | — | Jul 13, 2021 | Oct 15, 2023 | 1000 days past EOL | EOL |
| 9.5 | — | Apr 5, 2022 | May 1, 2024 | 801 days past EOL | EOL |
| 9.7 | — | Nov 8, 2022 | Dec 31, 2024 | 557 days past EOL | EOL |
| 10.0 | — | Jul 5, 2023 | Jul 5, 2024 | 736 days past EOL | EOL |
| 10.0_u1 | — | Aug 7, 2023 | Aug 7, 2024 | 703 days past EOL | EOL |
| 10.0_u2 | — | Nov 28, 2023 | Dec 31, 2024 | 557 days past EOL | EOL |
| 10.0_u3 | — | Feb 12, 2024 | Feb 12, 2026 | 149 days past EOL | EOL |
| 10.0_u4 | — | May 15, 2024 | May 15, 2026 | 57 days past EOL | EOL |
| 10.0_u5 | — | Aug 6, 2024 | Aug 6, 2026 | 26 days remaining | Warning |
| 10.0_u6 | — | Dec 3, 2024 | Dec 3, 2027 | 510 days remaining | Active |
| 10.0_u7 | — | May 6, 2025 | May 6, 2027 | 299 days remaining | Active |
| 10.8 | — | Oct 28, 2025 | Oct 28, 2027 | 474 days remaining | Active |
| 10.8.11 | — | Mar 3, 2026 | Mar 3, 2028 | 601 days remaining | Active |
| 10.9 | — | May 13, 2026 | May 13, 2028 | 672 days remaining | Active |
What does Zerto end of life mean for your organization?
When a version of Zerto 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Zerto versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Zerto has 16 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →