Raspberry Pi End of Life Dates
other
Developers working with single-board computers often rely on the Raspberry Pi, a credit-card sized device created in 2012 by the Raspberry Pi Foundation, a UK-based charity organization. The foundation maintains the Raspberry Pi, ensuring it remains a viable option for various projects, from robotics and home automation to media centers and retro game consoles. With its affordability and extensive community support, the Raspberry Pi has become a staple in the developer community, allowing users to focus on their projects without the burden of expensive hardware.
The Raspberry Pi has a total of 24 versions, with 4 of these versions having already reached their end-of-life, meaning they no longer receive support or security updates. Currently, 20 versions remain active, with the next end-of-life date scheduled for January 1, 2028, when version 3-b will cease to be supported. This information is crucial for developers who need to plan their projects and upgrades accordingly, ensuring they stay ahead of potential security risks and compatibility issues. By tracking the end-of-life dates of each Raspberry Pi version, developers can make informed decisions about their projects and avoid using outdated hardware.
When it comes to security, the Raspberry Pi has a spotless record, with no known Common Vulnerabilities and Exposures tracked. This means that none of the Raspberry Pi versions have any reported critical vulnerabilities, providing developers with a secure platform for their projects. As a result, there is no most affected version, and no action is required to address any known security issues. However, developers should still stay vigilant and monitor the security landscape, ensuring they are prepared to respond to any potential vulnerabilities that may arise in the future, and plan their upgrades and migrations to newer versions of the Raspberry Pi to maintain the security and integrity of their projects.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 5-500+ | Sep 25, 2025 | — | Jan 1, 2035 | in 3083d | — | — | Active | |
| 5-500 | Dec 9, 2024 | — | Jan 1, 2034 | in 2718d | — | — | Active | |
| cm5 | Nov 27, 2024 | — | Jan 1, 2036 | in 3448d | — | — | Active | |
| pico2 | Aug 8, 2024 | — | Jan 1, 2040 | in 4909d | — | — | Active | |
| 5 | Oct 23, 2023 | — | Jan 1, 2036 | in 3448d | — | — | Active | |
| cm4s | Apr 4, 2022 | — | Jan 1, 2034 | in 2718d | — | — | Active | |
| zero-2-w | Oct 28, 2021 | — | Jan 1, 2030 | in 1257d | — | — | Active | |
| pico | Jan 21, 2021 | — | Jan 1, 2036 | in 3448d | — | — | Active | |
| 4-400 | Nov 2, 2020 | — | Jan 1, 2028 | in 526d | — | — | Active | |
| cm4 | Oct 19, 2020 | — | Jan 1, 2034 | in 2718d | — | — | Active | |
| 4-b | Jun 24, 2019 | — | Jan 1, 2034 | in 2718d | — | — | Active | |
| cm3+ | Jan 28, 2019 | — | Jan 1, 2028 | in 526d | — | — | Active | |
| 3-a+ | Nov 15, 2018 | — | Jan 1, 2030 | in 1257d | — | — | Active | |
| 3-b+ | Mar 14, 2018 | — | Jan 1, 2030 | in 1257d | — | — | Active | |
| zero-w | Feb 28, 2017 | — | Jan 1, 2030 | in 1257d | — | — | Active | |
| cm3 | Jan 16, 2017 | — | Jan 1, 2028 | in 526d | — | — | Active | |
| 3-b | Feb 29, 2016 | — | Jan 1, 2028 | in 526d | — | — | Active | |
| zero | Nov 26, 2015 | — | Jan 1, 2030 | in 1257d | — | — | Active | |
| 2-b | Feb 2, 2015 | — | No | — | — | — | Active | |
| 1-a+ | Nov 10, 2014 | — | Jan 1, 2030 | in 1257d | — | — | Active | |
| 1-b+ | Jul 14, 2014 | — | Jan 1, 2030 | in 1257d | — | — | Active | |
| cm1 | Apr 7, 2014 | — | Jan 1, 2026 | 204d ago | — | — | EOL | |
| 1-a | Feb 4, 2013 | — | Nov 10, 2014 | 4274d ago | — | — | EOL | |
| 1-b | Mar 1, 2012 | — | Jul 14, 2014 | 4393d ago | — | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
