Complete end-of-life dates, support windows, and security status for all Raspberry Pi versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1-b | — | Mar 1, 2012 | Jul 14, 2014 | 4317 days past EOL | EOL |
| 1-a | — | Feb 4, 2013 | Nov 10, 2014 | 4198 days past EOL | EOL |
| cm1 | — | Apr 7, 2014 | Jan 1, 2026 | 128 days past EOL | EOL |
| 1-b+ | — | Jul 14, 2014 | Jan 1, 2030 | 1333 days remaining | Active |
| 1-a+ | — | Nov 10, 2014 | Jan 1, 2030 | 1333 days remaining | Active |
| 2-b | — | Feb 2, 2015 | Jan 1, 2026 | 128 days past EOL | EOL |
| zero | — | Nov 26, 2015 | Jan 1, 2030 | 1333 days remaining | Active |
| 3-b | — | Feb 29, 2016 | Jan 1, 2028 | 602 days remaining | Active |
| cm3 | — | Jan 16, 2017 | Jan 1, 2028 | 602 days remaining | Active |
| zero-w | — | Feb 28, 2017 | Jan 1, 2030 | 1333 days remaining | Active |
| 3-b+ | — | Mar 14, 2018 | Jan 1, 2030 | 1333 days remaining | Active |
| 3-a+ | — | Nov 15, 2018 | Jan 1, 2030 | 1333 days remaining | Active |
| cm3+ | — | Jan 28, 2019 | Jan 1, 2028 | 602 days remaining | Active |
| 4-b | — | Jun 24, 2019 | Jan 1, 2034 | 2794 days remaining | Active |
| cm4 | — | Oct 19, 2020 | Jan 1, 2034 | 2794 days remaining | Active |
| 4-400 | — | Nov 2, 2020 | Jan 1, 2028 | 602 days remaining | Active |
| pico | — | Jan 21, 2021 | Jan 1, 2036 | 3524 days remaining | Active |
| zero-2-w | — | Oct 28, 2021 | Jan 1, 2030 | 1333 days remaining | Active |
| cm4s | — | Apr 4, 2022 | Jan 1, 2034 | 2794 days remaining | Active |
| 5 | — | Oct 23, 2023 | Jan 1, 2036 | 3524 days remaining | Active |
| pico2 | — | Aug 8, 2024 | Jan 1, 2040 | 4985 days remaining | Active |
| cm5 | — | Nov 27, 2024 | Jan 1, 2036 | 3524 days remaining | Active |
| 5-500 | — | Dec 9, 2024 | Jan 1, 2034 | 2794 days remaining | Active |
| 5-500+ | — | Sep 25, 2025 | Jan 1, 2035 | 3159 days remaining | Active |
When a Raspberry Pi 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 Raspberry Pi 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 →