Longhorn · Lifecycle Status

Longhorn End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Longhorn versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Longhorn 1.8.2 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
1.8.2
1.8 series
Next EOL
None upcoming
Active Versions
4
of 11 total
EOL Versions
7
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2021202220232024202520261.11.21.31.41.51.61.71.81.91.101.11TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1.1 1.1.3 Dec 18, 2020 Apr 23, 2022 1477 days past EOL EOL
1.2 1.2.6 Aug 31, 2021 Oct 6, 2022 1311 days past EOL EOL
1.3 1.3.3 Jun 15, 2022 Aug 11, 2023 1002 days past EOL EOL
1.4 1.4.4 Dec 30, 2022 Mar 13, 2024 787 days past EOL EOL
1.5 1.5.5 Jul 7, 2023 Jul 19, 2024 659 days past EOL EOL
1.6 1.6.4 Feb 1, 2024 Mar 29, 2025 406 days past EOL EOL
1.7 1.7.3 Aug 20, 2024 Sep 4, 2025 247 days past EOL EOL
1.8 1.8.2 Jan 22, 2025 Already EOL Supported Active
1.9 1.9.2 May 27, 2025 Already EOL Supported Active
1.10 1.10.2 Sep 25, 2025 Already EOL Supported Active
1.11 1.11.2 Jan 29, 2026 Already EOL Supported Active

What does Longhorn end of life mean for your organization?

When a Longhorn version 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 Longhorn 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Longhorn?
See the full table above for all Longhorn version EOL dates.
What is the latest supported version of Longhorn?
The latest active version of Longhorn is 1.8.2. Always verify against the table above as support windows can change.
What happens when Longhorn reaches end of life?
When Longhorn reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Longhorn?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Longhorn versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →