LineageOS End of Life (EOL) Dates & Support Timeline
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.
LineageOS 23.2 is supported, with no end-of-life or end-of-support date announced yet. 11 of 13 tracked LineageOS versions are past end of life; the most recent to reach it, 23.0, did so on February 28, 2026. The full LineageOS lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 13.0 | — | Jan 22, 2017 | Feb 12, 2018 | 3146 days past EOL | EOL |
| 14.1 | — | Jan 22, 2017 | Feb 25, 2019 | 2768 days past EOL | EOL |
| 15.1 | — | Feb 25, 2018 | Feb 28, 2020 | 2400 days past EOL | EOL |
| 16.0 | — | Mar 1, 2019 | Feb 16, 2021 | 2046 days past EOL | EOL |
| 17.1 | — | Feb 1, 2020 | Apr 26, 2022 | 1612 days past EOL | EOL |
| 18.1 | — | Apr 1, 2021 | Mar 5, 2024 | 933 days past EOL | EOL |
| 19 | — | Apr 26, 2022 | Feb 14, 2024 | 953 days past EOL | EOL |
| 20 | — | Dec 31, 2022 | Dec 31, 2024 | 632 days past EOL | EOL |
| 21 | — | Feb 14, 2024 | Oct 12, 2025 | 347 days past EOL | EOL |
| 22.1 | — | Dec 31, 2024 | May 13, 2025 | 499 days past EOL | EOL |
| 22.2 | — | Apr 11, 2025 | TBD | Supported | Active |
| 23.0 | — | Oct 11, 2025 | Feb 28, 2026 | 208 days past EOL | EOL |
| 23.2 | — | Feb 8, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/lineageos)
LineageOS release and support pattern
Across the 13 release lines with a published release date, LineageOS has shipped a new line roughly every 11 months (median interval). A line typically stays supported for about 2 years from its release to its end-of-life date (measured on the 11 lines with both dates published).
Of the 13 release lines tracked, 11 are past end of life and 2 are still within support. The newest line, 23.2, was released February 8, 2026. No end-of-life date is currently published for the 2 supported lines.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does LineageOS end of life mean for your organization?
When a version of LineageOS 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps 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.
Your options when LineageOS reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for LineageOS from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →