Complete end-of-life dates, support windows, and security status for all Yocto versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.7 | 2.7.4 | May 1, 2019 | Jun 1, 2020 | 2168 days past EOL | EOL |
| 3.0 | 3.0.4 | Oct 22, 2019 | Aug 1, 2020 | 2107 days past EOL | EOL |
| 3.1 LTS | 3.1.33 | Apr 21, 2020 | Apr 30, 2024 | 739 days past EOL | EOL |
| 3.2 | 3.2.4 | Nov 3, 2020 | May 1, 2021 | 1834 days past EOL | EOL |
| 3.3 | 3.3.6 | Apr 19, 2021 | Apr 20, 2022 | 1480 days past EOL | EOL |
| 3.4 | 3.4.4 | Oct 25, 2021 | May 1, 2022 | 1469 days past EOL | EOL |
| 4.0 LTS | 4.0.35 | Apr 25, 2022 | Apr 27, 2026 | 12 days past EOL | EOL |
| 4.1 | 4.1.4 | Oct 23, 2022 | May 27, 2023 | 1078 days past EOL | EOL |
| 4.2 | 4.2.4 | May 3, 2023 | Nov 5, 2023 | 916 days past EOL | EOL |
| 4.3 | 4.3.4 | Nov 9, 2023 | Jun 9, 2024 | 699 days past EOL | EOL |
| 5.0 LTS | 5.0.17 | Apr 29, 2024 | Apr 30, 2028 | 722 days remaining | Active |
| 5.1 | 5.1.4 | Oct 16, 2024 | May 16, 2025 | 358 days past EOL | EOL |
| 5.2 | 5.2.4 | May 7, 2025 | Dec 7, 2025 | 153 days past EOL | EOL |
| 5.3 | 5.3 | Dec 15, 2025 | Jun 15, 2026 | 37 days remaining | Warning |
When a Yocto 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 Yocto 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 →