Longhorn End of Life Dates
other
Developers rely on Longhorn to streamline their workflow, and for good reason - this tool has been a cornerstone of efficient development since its inception. Created to address the need for effective end-of-life tracking, Longhorn has been diligently maintained to ensure it continues to meet the evolving needs of its users. With a rich history and a strong maintenance team behind it, Longhorn has become an essential resource for those looking to stay on top of supported versions and security patch timelines. By providing a clear picture of when each release reaches end of support, Longhorn enables developers to plan their upgrades with confidence.
The Longhorn landscape is characterized by a total of 12 versions, with 7 of these having already reached end-of-life. Currently, 5 versions remain active, with the latest stable version being 1.12.0. As the landscape continues to shift, developers should be aware that the next version slated for end-of-life is 1.8, which will expire on 2026-07-22. This follows the last end-of-life date, which occurred on 2025-09-04 for version 1.7. By keeping a close eye on these timelines, developers can ensure they are always running a supported version of Longhorn.
From a security perspective, Longhorn has a spotless record, with a total of 0 CVEs tracked and 0 critical CVEs. As a result, there is no most affected version to speak of. With no known vulnerabilities to contend with, developers can focus on their work without worrying about potential security risks. However, it is still essential to stay up-to-date with the latest versions and security patches to ensure the continued stability and security of their systems. By taking proactive steps to stay current, developers can minimize potential risks and ensure they are always running a secure and supported version of Longhorn.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.12 | Jun 2, 2026 | — | Dec 2, 2027 | in 496d | 1.12.0 | — | Active | |
| 1.11 | Jan 29, 2026 | — | Jul 29, 2027 | in 370d | 1.11.3 | — | Active | |
| 1.10 | Sep 25, 2025 | — | Mar 25, 2027 | in 244d | 1.10.2 | — | Active | |
| 1.9 | May 27, 2025 | — | Nov 27, 2026 | in 126d | 1.9.2 | — | Active | |
| 1.8 | Jan 22, 2025 | — | Jul 22, 2026 | 2d ago | 1.8.2 | — | EOL | |
| 1.7 | Aug 20, 2024 | — | Sep 4, 2025 | 323d ago | 1.7.3 | — | EOL | |
| 1.6 | Feb 1, 2024 | — | Mar 29, 2025 | 482d ago | 1.6.4 | — | EOL | |
| 1.5 | Jul 7, 2023 | — | Jul 19, 2024 | 735d ago | 1.5.5 | — | EOL | |
| 1.4 | Dec 30, 2022 | — | Mar 13, 2024 | 863d ago | 1.4.4 | — | EOL | |
| 1.3 | Jun 15, 2022 | — | Aug 11, 2023 | 1078d ago | 1.3.3 | — | EOL | |
| 1.2 | Aug 31, 2021 | — | Oct 6, 2022 | 1387d ago | 1.2.6 | — | EOL | |
| 1.1 | Dec 18, 2020 | — | Apr 23, 2022 | 1553d ago | 1.1.3 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
