Longhorn 1.13 · Version Status
Longhorn 1.13 End of Life Date
Longhorn 1.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.
✓
Longhorn 1.13 is actively supported. EOL date: November 29, 2027.
📅 Get reminded before Longhorn 1.13 reaches EOL on November 29, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 29, 2027
425 days remaining
Latest Release
1.13.0
Standard release
Release Date
Sep 29, 2026
Longhorn 1.13 series
Lifecycle detail
Longhorn 1.13 was released on September 29, 2026 and support is scheduled to end on November 29, 2027 — a planned supported lifespan of 1 year and 2 months, in line with the 1 year and 2 months median for Longhorn releases. Its most recent patch is 1.13.0, published September 29, 2026.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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 →
| Version | Latest | EOL Date | Status |
|---|
| 1.1 |
1.1.3 |
Apr 23, 2022 |
EOL |
| 1.2 |
1.2.6 |
Oct 6, 2022 |
EOL |
| 1.3 |
1.3.3 |
Aug 11, 2023 |
EOL |
| 1.4 |
1.4.4 |
Mar 13, 2024 |
EOL |
| 1.5 |
1.5.5 |
Jul 19, 2024 |
EOL |
| 1.6 |
1.6.4 |
Mar 29, 2025 |
EOL |
| 1.7 |
1.7.3 |
Sep 4, 2025 |
EOL |
| 1.8 |
1.8.2 |
Jul 22, 2026 |
EOL |
What does Longhorn 1.13 end of life mean?
When Longhorn 1.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 Longhorn 1.13 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Longhorn 1.13 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Longhorn 1.13 reach end of life?
Longhorn 1.13 reached end of life on November 29, 2027. That is 425 days remaining.
Is Longhorn 1.13 still supported?
Yes, Longhorn 1.13 is currently supported. The EOL date is November 29, 2027.
What should I upgrade to from Longhorn 1.13?
The recommended upgrade from Longhorn 1.13 is
Longhorn 1.13 — the latest actively supported version. Check the
Longhorn full timeline for all supported versions.
What are the security risks of running Longhorn 1.13 past EOL?
When Longhorn 1.13 reaches end of life, the maintainers stop issuing 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 Longhorn should migrate immediately or implement compensating controls.