Yocto End of Life Dates
other
Developers working with embedded Linux systems rely on a robust framework to streamline their development process, which is where Yocto comes into play, having been created to address the complexities of building custom Linux distributions. Maintained by the Yocto Project, an open-source collaboration, this tool has been a cornerstone for embedded system development since its inception. The Yocto Project's community-driven approach ensures that developers have access to a stable and secure platform for their projects, which is why many developers utilize Yocto for its flexibility and customizability.
The end-of-life landscape for Yocto is characterized by a total of 14 versions, with 12 of these versions having reached their end-of-life, leaving only 2 active versions currently supported. The latest stable version, 5.3, is slated to reach its end-of-life on 2026-06-15, marking an important milestone for developers who must plan their upgrades accordingly to ensure continuity and security. Prior to this, version 4.0 reached its end-of-life on 2026-04-27, underscoring the ongoing cycle of support and maintenance that defines the Yocto ecosystem.
Given the current security posture, Yocto presents a favorable picture with 0 total CVEs tracked and 0 critical CVEs, resulting in no most affected version. This security profile indicates a robust and secure framework, which is essential for developers working on critical embedded systems. Furthermore, with no known vulnerabilities, Yocto does not currently have a KEV status, reinforcing its stance as a reliable choice for development. To maintain this level of security, developers should stay informed about upcoming end-of-life dates and plan their migrations to newer, supported versions, such as the latest stable version, to ensure their projects remain secure and up-to-date.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 6.0 LTS | May 13, 2026 | — | Apr 30, 2030 | in 1376d | 6.0.1 | — | Active | |
| 5.3 | Dec 15, 2025 | — | Jun 15, 2026 | 39d ago | 5.3 | — | EOL | |
| 5.2 | May 7, 2025 | — | Dec 7, 2025 | 229d ago | 5.2.4 | — | EOL | |
| 5.1 | Oct 16, 2024 | — | May 16, 2025 | 434d ago | 5.1.4 | — | EOL | |
| 5.0 LTS | Apr 29, 2024 | — | Apr 30, 2028 | in 646d | 5.0.19 | — | Active | |
| 4.3 | Nov 9, 2023 | — | Jun 9, 2024 | 775d ago | 4.3.4 | — | EOL | |
| 4.2 | May 3, 2023 | — | Nov 5, 2023 | 992d ago | 4.2.4 | — | EOL | |
| 4.1 | Oct 23, 2022 | — | May 27, 2023 | 1154d ago | 4.1.4 | — | EOL | |
| 4.0 LTS | Apr 25, 2022 | — | Apr 27, 2026 | 88d ago | 4.0.35 | — | EOL | |
| 3.4 | Oct 25, 2021 | — | May 1, 2022 | 1545d ago | 3.4.4 | — | EOL | |
| 3.3 | Apr 19, 2021 | — | Apr 20, 2022 | 1556d ago | 3.3.6 | — | EOL | |
| 3.2 | Nov 3, 2020 | — | May 1, 2021 | 1910d ago | 3.2.4 | — | EOL | |
| 3.1 LTS | Apr 21, 2020 | — | Apr 30, 2024 | 815d ago | 3.1.33 | — | EOL | |
| 3.0 | Oct 22, 2019 | — | Aug 1, 2020 | 2183d ago | 3.0.4 | — | EOL | |
| 2.7 | May 1, 2019 | — | Jun 1, 2020 | 2244d ago | 2.7.4 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
