Lineageos End of Life Dates
other
Developers working with custom Android operating systems rely on a specific set of tools to manage and maintain their projects, and one such tool is used to track the life cycle of various operating system versions. Lineageos is a custom operating system that provides regular security updates and feature enhancements, and tracking its end-of-life dates is crucial for maintaining the security and stability of projects that use it. The team behind Lineageos works tirelessly to ensure that each version receives the necessary support and updates, and this dedication has led to its widespread adoption among developers. With a history spanning multiple versions, Lineageos has become a staple in the custom Android operating system community.
The end-of-life landscape for Lineageos is characterized by a large number of versions that have already reached the end of their support cycle, with 11 out of 13 total versions no longer receiving updates. This leaves only 2 active versions that are currently supported, highlighting the need for developers to stay up-to-date with the latest versions to ensure they receive the latest security patches and feature enhancements. Although the next end-of-life date is not currently specified, the last version to reach end-of-life was version 21, which occurred on 2025-10-12. This emphasizes the importance of regularly reviewing the support status of each Lineageos version to plan upgrades and migrations accordingly.
In terms of security, the picture for Lineageos is relatively clean, with no known CVEs currently tracked. This means that there are no critical vulnerabilities that developers need to be aware of, providing a sense of security and stability for projects that use Lineageos. As a result, developers can focus on building and maintaining their projects without worrying about addressing potential security vulnerabilities. However, it is still essential for developers to stay vigilant and monitor the security landscape for any changes, ensuring that they can respond quickly to any newly discovered vulnerabilities and keep their projects secure.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 23.2 | Feb 8, 2026 | — | No | — | — | — | Active | |
| 23.0 | Oct 11, 2025 | — | Yes | — | — | — | EOL | |
| 22.2 | Apr 11, 2025 | — | No | — | — | — | Active | |
| 22.1 | Dec 31, 2024 | — | Yes | — | — | — | EOL | |
| 21 | Feb 14, 2024 | — | Oct 12, 2025 | 285d ago | — | — | EOL | |
| 20 | Dec 31, 2022 | — | Yes | — | — | — | EOL | |
| 19 | Apr 26, 2022 | — | Feb 14, 2024 | 891d ago | — | — | EOL | |
| 18.1 | Apr 1, 2021 | — | Mar 5, 2024 | 871d ago | — | — | EOL | |
| 17.1 | Feb 1, 2020 | — | Apr 26, 2022 | 1550d ago | — | — | EOL | |
| 16.0 | Mar 1, 2019 | — | Feb 16, 2021 | 1984d ago | — | — | EOL | |
| 15.1 | Feb 25, 2018 | — | Yes | — | — | — | EOL | |
| 14.1 | Jan 22, 2017 | — | Yes | — | — | — | EOL | |
| 13.0 | Jan 22, 2017 | — | Yes | — | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
