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.
Zerto 10.9 is supported until May 13, 2028, its end-of-support date. Active support for Zerto 10.9 ends on May 13, 2027; security fixes continue until that end-of-life date. The next Zerto version to reach end of life is 10.0 Update 7, on May 6, 2027. 17 of 22 tracked Zerto versions are past end of life; the most recent to reach it, 10.0 Update 5, did so on August 6, 2026. The full Zerto lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 5.0 | — | Nov 8, 2016 | Aug 31, 2018 | 2945 days past EOL | EOL |
| 5.5 | — | Jul 31, 2017 | Sep 30, 2019 | 2550 days past EOL | EOL |
| 6.0 | — | Feb 15, 2018 | Mar 30, 2020 | 2368 days past EOL | EOL |
| 6.5 | — | Sep 16, 2018 | Oct 30, 2020 | 2154 days past EOL | EOL |
| 7.0 | — | Apr 26, 2019 | May 30, 2021 | 1942 days past EOL | EOL |
| 7.5 | — | Sep 22, 2019 | Dec 6, 2021 | 1752 days past EOL | EOL |
| 8.0 | — | Mar 22, 2020 | Jun 1, 2022 | 1575 days past EOL | EOL |
| 8.5 | — | Nov 1, 2020 | Jan 1, 2023 | 1361 days past EOL | EOL |
| 9.0 | — | Jul 13, 2021 | Oct 15, 2023 | 1074 days past EOL | EOL |
| 9.5 | — | Apr 5, 2022 | May 1, 2024 | 875 days past EOL | EOL |
| 9.7 | — | Nov 8, 2022 | Dec 31, 2024 | 631 days past EOL | EOL |
| 10.0 | — | Jul 5, 2023 | Jul 5, 2024 | 810 days past EOL | EOL |
| 10.0 Update 1 | — | Aug 7, 2023 | Aug 7, 2024 | 777 days past EOL | EOL |
| 10.0 Update 2 | — | Nov 28, 2023 | Dec 31, 2024 | 631 days past EOL | EOL |
| 10.0 Update 3 | — | Feb 12, 2024 | Feb 12, 2026 | 223 days past EOL | EOL |
| 10.0 Update 4 | — | May 15, 2024 | May 15, 2026 | 131 days past EOL | EOL |
| 10.0 Update 5 | — | Aug 6, 2024 | Aug 6, 2026 | 48 days past EOL | EOL |
| 10.0 Update 6 | — | Dec 3, 2024 | Dec 3, 2027 | 436 days remaining | Active |
| 10.0 Update 7 | — | May 6, 2025 | May 6, 2027 | 225 days remaining | Active |
| 10.8 | — | Oct 28, 2025 | Oct 28, 2027 | 400 days remaining | Active |
| 10.8.11 | — | Mar 3, 2026 | Mar 3, 2028 | 527 days remaining | Active |
| 10.9 | — | May 13, 2026 | May 13, 2028 | 598 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/zerto)
Zerto lifecycle status — the real story
Zerto publishes its support rules in a Product Version Lifecycle Matrix on its documentation portal, which lists each version's support phases and end dates; the dates above are taken from that matrix via our upstream data. The matrix sits behind Zerto's portal rather than a public page, so verify your specific version's dates there.
Verified against the vendor's lifecycle documentation on August 22, 2026.
Zerto release and support pattern
Of the 22 release lines tracked, 17 are past end of life and 5 are still within support. The newest line, 10.9, was released May 13, 2026. The next scheduled end of life is 10.0_u7 on May 6, 2027 — 225 days from this build. The longest-supported line currently published is 10.9, to May 13, 2028.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.
Your options when Zerto reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
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 17 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Zerto is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."