Complete end-of-life dates, support windows, and security status for all Rancher versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.6 | 1.6.30 | May 4, 2017 | Jun 30, 2020 | 2139 days past EOL | EOL |
| 2.0 | 2.0.16 | Apr 30, 2018 | Nov 1, 2019 | 2381 days past EOL | EOL |
| 2.1 | 2.1.14 | Oct 5, 2018 | Apr 19, 2020 | 2211 days past EOL | EOL |
| 2.2 | 2.2.13 | Mar 25, 2019 | Oct 15, 2020 | 2032 days past EOL | EOL |
| 2.3 | 2.3.11 | Oct 7, 2019 | Apr 7, 2021 | 1858 days past EOL | EOL |
| 2.4 | 2.4.18 | Mar 30, 2020 | Mar 31, 2022 | 1500 days past EOL | EOL |
| 2.5 | 2.5.17 | Oct 5, 2020 | Jan 31, 2023 | 1194 days past EOL | EOL |
| 2.6 | 2.6.14 | Aug 30, 2021 | Apr 30, 2024 | 739 days past EOL | EOL |
| 2.7 | 2.7.18 | Nov 16, 2022 | Nov 18, 2024 | 537 days past EOL | EOL |
| 2.8 | 2.8.15 | Dec 5, 2023 | Jul 22, 2025 | 291 days past EOL | EOL |
| 2.9 | 2.9.12 | Aug 26, 2024 | Feb 26, 2026 | 72 days past EOL | EOL |
| 2.10 | 2.10.11 | Dec 19, 2024 | Jun 19, 2026 | 41 days remaining | Warning |
| 2.11 | 2.11.13 | Apr 24, 2025 | Oct 24, 2026 | 168 days remaining | Warning |
| 2.12 | 2.12.9 | Aug 29, 2025 | Feb 28, 2027 | 295 days remaining | Active |
| 2.13 | 2.13.5 | Dec 17, 2025 | Jun 17, 2027 | 404 days remaining | Active |
| 2.14 | 2.14.1 | Apr 30, 2026 | Oct 10, 2027 | 519 days remaining | Active |
When a Rancher 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 Rancher 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →