Horizon 8.2606 · Version Status

Horizon 8.2606 End of Life Date

Horizon 8.2606 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Horizon 8.2606 is actively supported. EOL date: August 24, 2029.
📅 Get reminded before Horizon 8.2606 reaches EOL on August 24, 2029 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Aug 24, 2029
1093 days remaining
Latest Release
8.2606
Standard release
Release Date
Aug 24, 2026
Horizon 8.2606 series
Lifecycle detail

Horizon 8.2606 was released on August 24, 2026 and support is scheduled to end on August 24, 2029 — a planned supported lifespan of 3 years, in line with the 3 years median for Horizon releases. It is not an LTS release; Horizon reserves longer patch windows for its LTS versions. Its most recent patch is 8.2606, published August 24, 2026.

← Horizon 8.2603 All Horizon versions
30 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Horizon Versions
VersionLatestEOL DateStatus
7.X NonLTS branch 7.13.2 Apr 30, 2023 EOL
7.5 LTS 7.5.4 Nov 30, 2020 EOL
7.10 LTS 7.10.3 Mar 17, 2022 EOL
8.2006 8.2006 Aug 11, 2025 EOL
8.2012 8.2012 Jan 7, 2024 EOL
8.2103 8.2103 Mar 23, 2024 EOL
8.2106 8.2106 Jul 15, 2024 EOL
8.2111 LTS 8.2111.3 Nov 30, 2024 EOL

What does Horizon 8.2606 end of life mean?

When Horizon 8.2606 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Horizon 8.2606 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Horizon 8.2606 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Horizon 8.2606 reach end of life?
Horizon 8.2606 reached end of life on August 24, 2029. That is 1093 days remaining.
Is Horizon 8.2606 still supported?
Yes, Horizon 8.2606 is currently supported. The EOL date is August 24, 2029.
What should I upgrade to from Horizon 8.2606?
The recommended upgrade from Horizon 8.2606 is Horizon 8.2606 — the latest actively supported version. Check the Horizon full timeline for all supported versions.
What are the security risks of running Horizon 8.2606 past EOL?
When Horizon 8.2606 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Horizon should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →