Oneplus End of Life Dates
other
Developers rely on accurate and timely information to manage their projects effectively, particularly when it comes to tracking end-of-life dates for the devices they support, such as Oneplus. Created to provide a centralized resource for this purpose, the Oneplus end-of-life tracking website offers a comprehensive overview of supported versions and security patch timelines. Maintained by dedicated professionals, this website aims to empower developers with the knowledge they need to plan upgrades and ensure seamless continuity for their applications. With its inception, the website has been bridging the gap between device manufacturers and developers, facilitating a more coordinated approach to software maintenance.
The landscape of Oneplus versions currently comprises a total of 12 versions, out of which 1 has already reached its end-of-life, leaving 11 active versions. As of the latest updates, version 11 is slated to be the next to expire, with its end-of-life date set for 2028-02-07. This timeline is crucial for developers to prepare and migrate their applications to newer, supported versions. The most recent version to have reached its end-of-life was version pad1, which occurred on 2026-05-01, marking an important milestone in the lifecycle of Oneplus devices. Understanding these timelines is essential for maintaining the security and compatibility of applications developed for these devices.
From a security standpoint, the Oneplus ecosystem currently shows a clean slate, with 0 CVEs tracked and no critical vulnerabilities reported. This positive security posture indicates that Oneplus devices have not been significantly impacted by known security flaws. As a result, there is no most affected version to highlight, and the KEV status is not applicable in this context. Despite this favorable situation, developers should remain vigilant and proactive, ensuring they stay informed about any future security patches or updates that may affect the Oneplus devices their applications support. By doing so, they can take appropriate action to safeguard their users and maintain the integrity of their applications.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 15r | Dec 22, 2025 | Dec 22, 2029 | Dec 31, 2031 | in 1986d | — | — | Active | |
| 15 | Nov 13, 2025 | Nov 13, 2029 | Nov 13, 2031 | in 1938d | — | — | Active | |
| pad3 | Jun 5, 2025 | Jun 5, 2029 | Jun 19, 2031 | in 1791d | — | — | Active | |
| 13t | Apr 24, 2025 | Apr 24, 2029 | Apr 24, 2031 | in 1735d | — | — | Active | |
| 13r | Jan 7, 2025 | Jan 7, 2029 | Jan 7, 2031 | in 1628d | — | — | Active | |
| 13 | Oct 31, 2024 | Oct 31, 2028 | Oct 31, 2030 | in 1560d | — | — | Active | |
| pad2 | Jul 16, 2024 | Jul 16, 2027 | Jul 16, 2028 | in 723d | — | — | Active | |
| 12r | Jan 23, 2024 | Jan 23, 2028 | Jan 23, 2029 | in 914d | — | — | Active | |
| 12 | Jan 23, 2024 | Jan 23, 2028 | Jan 23, 2029 | in 914d | — | — | Active | |
| pad1 | May 1, 2023 | May 1, 2026 | May 1, 2026 | 84d ago | — | — | EOL | |
| 11r | Feb 7, 2023 | Feb 7, 2027 | Feb 7, 2028 | in 563d | — | — | Active | |
| 11 | Feb 7, 2023 | Feb 7, 2027 | Feb 7, 2028 | in 563d | — | — | Active |
Data sourced from endoflife.date · CVE data from NVD
