Complete end-of-life dates, support windows, and security status for all Lineageos versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 13.0 | — | Jan 22, 2017 | Supported indefinitely | Supported | Active |
| 14.1 | — | Jan 22, 2017 | Supported indefinitely | Supported | Active |
| 15.1 | — | Feb 25, 2018 | Supported indefinitely | Supported | Active |
| 16.0 | — | Mar 1, 2019 | Feb 16, 2021 | 1908 days past EOL | EOL |
| 17.1 | — | Feb 1, 2020 | Apr 26, 2022 | 1474 days past EOL | EOL |
| 18.1 | — | Apr 1, 2021 | Mar 5, 2024 | 795 days past EOL | EOL |
| 19 | — | Apr 26, 2022 | Feb 14, 2024 | 815 days past EOL | EOL |
| 20 | — | Dec 31, 2022 | Supported indefinitely | Supported | Active |
| 21 | — | Feb 14, 2024 | Oct 12, 2025 | 209 days past EOL | EOL |
| 22.1 | — | Dec 31, 2024 | Supported indefinitely | Supported | Active |
| 22.2 | — | Apr 11, 2025 | Already EOL | Supported | Active |
| 23.0 | — | Oct 11, 2025 | Supported indefinitely | Supported | Active |
| 23.2 | — | Feb 8, 2026 | Already EOL | Supported | Active |
When a Lineageos 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 Lineageos 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 →