Horizon 7.13 · Version Status
Horizon 7.13 End of Life Date
Horizon 7.13 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Horizon 7.13 is past end of life. This version no longer receives security patches. 1271 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 30, 2023
1271 days past EOL
Latest Release
7.13.3
Standard release
Release Date
Oct 15, 2020
Horizon 7.13 series
Where these dates come from
End of lifeApr 30, 2023Vendor's own page, read by our adapter · docs.omnissa.com · checked Oct 20, 2026high · 2 sources agree ReleaseOct 15, 2020Vendor's own page, read by our adapter · docs.omnissa.com · checked Oct 20, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Horizon 7.13 was released on October 15, 2020 and support ended on April 30, 2023 — a supported lifespan of 2 years and 7 months, shorter than the 3 years median for Horizon releases. It was not an LTS release; Horizon reserves longer patch windows for its LTS versions. The last patch it will ever receive is 7.13.3, published March 21, 2023 — 40 days before support ended. It has been without security patches for 3 years and 6 months. 10 newer Horizon releases have shipped since.
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 →
Extended Support
Extended Horizon 7.13 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 7.X NonLTS branch |
7.13.3 |
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 |
| → 7.13 |
7.13.3 |
Apr 30, 2023 |
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 |
What does Horizon 7.13 end of life mean?
When Horizon 7.13 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Horizon 7.13 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 7.13 reach end of life?
Horizon 7.13 reached end of life on April 30, 2023. This version is no longer receiving security patches.
Is Horizon 7.13 still supported?
No. Horizon 7.13 reached end of life on April 30, 2023 and is no longer receiving security patches.
What should I upgrade to from Horizon 7.13?
The recommended upgrade from Horizon 7.13 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 7.13 past EOL?
Since Horizon 7.13 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Horizon should migrate immediately or implement compensating controls.