Horizon End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Horizon versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 7.X NonLTS branch | 7.13.2 | Mar 22, 2016 | Apr 30, 2023 | 1197 days past EOL | EOL |
| 7.5 LTS | 7.5.4 | May 29, 2018 | Nov 30, 2020 | 2078 days past EOL | EOL |
| 7.10 LTS | 7.10.3 | Sep 17, 2019 | Mar 17, 2022 | 1606 days past EOL | EOL |
| 8.2006 | 8.2006 | Aug 11, 2020 | Aug 11, 2025 | 363 days past EOL | EOL |
| 8.2012 | 8.2012 | Jan 7, 2021 | Jan 7, 2024 | 945 days past EOL | EOL |
| 8.2103 | 8.2103 | Mar 23, 2021 | Mar 23, 2024 | 869 days past EOL | EOL |
| 8.2106 | 8.2106 | Jul 15, 2021 | Jul 15, 2024 | 755 days past EOL | EOL |
| 8.2111 LTS | 8.2111.2 | Nov 30, 2021 | Nov 30, 2024 | 617 days past EOL | EOL |
| 8.2203 | 8.2203 | Apr 5, 2022 | Apr 5, 2025 | 491 days past EOL | EOL |
| 8.2206 | 8.2206 | Jul 19, 2022 | Jul 19, 2025 | 386 days past EOL | EOL |
| 8.2209 | 8.2209.1 | Oct 20, 2022 | Oct 20, 2025 | 293 days past EOL | EOL |
| 8.2212 LTS | 8.2212.2 | Jan 12, 2023 | Jul 12, 2026 | 28 days past EOL | EOL |
| 8.2303 | 8.2303 | Mar 30, 2023 | Mar 30, 2026 | 132 days past EOL | EOL |
| 8.2306 | 8.2306 | Jul 6, 2023 | Jul 6, 2026 | 34 days past EOL | EOL |
| 8.2309 | 8.2309 | Oct 26, 2023 | Oct 26, 2026 | 78 days remaining | Warning |
| 8.2312 LTS | 8.2312.1 | Jan 23, 2024 | Jan 23, 2027 | 167 days remaining | Warning |
| 8.2406 | 8.2406 | Jul 25, 2024 | Jul 25, 2027 | 350 days remaining | Active |
| 8.2412 | 8.2412 | Jan 28, 2025 | Jan 28, 2028 | 537 days remaining | Active |
| 8.2503 LTS | 8.2503.2 | Apr 15, 2025 | Apr 15, 2028 | 615 days remaining | Active |
| 8.2506 | 8.2506.1 | Jul 31, 2025 | Jul 31, 2028 | 722 days remaining | Active |
| 8.2512 | 8.2512.1 | Dec 16, 2025 | Dec 16, 2028 | 860 days remaining | Active |
| 8.2603 LTS | 8.2603 | Apr 14, 2026 | Apr 14, 2029 | 979 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/horizon)
What does Horizon end of life mean for your organization?
When a version of Horizon 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 Horizon 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 Horizon 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Horizon versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Horizon has 14 versions past end of life — security patches have stopped, but CVE disclosures haven't. The good news: extended support for Horizon exists — vetted vendors ship security patches for years past the official date. Tell us where to reach you and we'll reply with matched options and pricing guidance.