Bitcoin Core End of Life Dates
other
Developers working with cryptocurrency rely on a robust and secure platform to manage bitcoin transactions, and Bitcoin Core has been a cornerstone of this ecosystem since its inception. As the reference implementation of bitcoin, it provides a comprehensive bitcoin node and wallet, ensuring payments are fully verified. The open-source nature of Bitcoin Core allows for community-driven maintenance, with a dedicated team of developers contributing to its ongoing development and support. This collaborative approach has fostered a high level of trust among developers, who value the software's reliability and security in managing bitcoin transactions.
The end-of-life landscape for Bitcoin Core is characterized by a large number of versions, with 24 releases to date, of which 21 have reached their end-of-life. Currently, three versions remain active, with the latest stable version being 29.3. Notably, the most recent end-of-life date was April 19, 2026, for version 28, but there is no scheduled end-of-life date for upcoming versions. This provides developers with a stable foundation for their applications, knowing that they can rely on the current versions without imminent concerns about expiration.
The security profile of Bitcoin Core is exceptionally strong, with no recorded Common Vulnerabilities and Exposures (CVEs), indicating a robust and secure codebase. As a result, there are no critical CVEs, and no version is disproportionately affected by vulnerabilities. The absence of CVEs also means that Bitcoin Core is not listed on the Known Exploited Vulnerabilities (KEV) catalog. Given this exemplary security record, developers can confidently utilize Bitcoin Core for their bitcoin transactions, focusing on developing their applications without undue concern for potential security risks associated with the platform.
Last updated: Jul 24, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 31 | Apr 19, 2026 | Apr 20, 2026 | No | — | 31.1 | — | Active | |
| 30 | Oct 10, 2025 | Oct 10, 2025 | No | — | 30.3 | — | Active | |
| 29 | Apr 14, 2025 | Oct 10, 2025 | No | — | 29.4 | — | Active | |
| 28 | Oct 2, 2024 | Oct 10, 2025 | Apr 19, 2026 | 96d ago | 28.4 | — | EOL | |
| 27 | Apr 16, 2024 | Apr 14, 2025 | Oct 10, 2025 | 287d ago | 27.2 | — | EOL | |
| 26 | Dec 6, 2023 | Oct 2, 2024 | Apr 14, 2025 | 466d ago | 26.2 | — | EOL | |
| 25 | May 18, 2023 | Apr 16, 2024 | Oct 2, 2024 | 660d ago | 25.2 | — | EOL | |
| 24 | Nov 24, 2022 | Dec 12, 2023 | Apr 2, 2024 | 843d ago | 24.2 | — | EOL | |
| 23 | Apr 25, 2022 | May 18, 2023 | Dec 1, 2023 | 966d ago | 23.2 | — | EOL | |
| 22 | Sep 13, 2021 | Dec 14, 2022 | Apr 1, 2023 | 1210d ago | 22.1 | — | EOL | |
| 0.21 | Jan 15, 2021 | Apr 25, 2022 | Oct 1, 2022 | 1392d ago | 0.21.2 | — | EOL | |
| 0.20 | Jun 3, 2020 | Sep 13, 2021 | Feb 1, 2022 | 1634d ago | 0.20.2 | — | EOL | |
| 0.19 | Nov 24, 2019 | Jan 15, 2021 | Aug 1, 2021 | 1818d ago | 0.19.2 | — | EOL | |
| 0.18 | May 2, 2019 | Jun 3, 2020 | Feb 1, 2021 | 1999d ago | 0.18.1 | — | EOL | |
| 0.17 | Oct 3, 2018 | Nov 24, 2019 | Aug 1, 2020 | 2183d ago | 0.17.2 | — | EOL | |
| 0.16 | Feb 26, 2018 | May 2, 2019 | Feb 1, 2020 | 2365d ago | 0.16.3 | — | EOL | |
| 0.15 | Sep 15, 2017 | Oct 3, 2018 | Aug 1, 2019 | 2549d ago | 0.15.2 | — | EOL | |
| 0.14 | Mar 8, 2017 | Feb 26, 2018 | Feb 1, 2019 | 2730d ago | 0.14.3 | — | EOL | |
| 0.13 | Aug 23, 2016 | Sep 15, 2017 | Aug 1, 2018 | 2914d ago | 0.13.2 | — | EOL | |
| 0.12 | Feb 23, 2016 | Mar 31, 2017 | Feb 28, 2018 | 3068d ago | 0.12.1 | — | EOL | |
| 0.11 | Jul 12, 2015 | Aug 23, 2016 | Aug 1, 2017 | 3279d ago | 0.11.3 | — | EOL | |
| 0.10 | Feb 16, 2015 | Feb 29, 2016 | Feb 28, 2017 | 3433d ago | 0.10.5 | — | EOL | |
| 0.9 | Mar 19, 2014 | Jun 16, 2015 | Feb 28, 2016 | 3799d ago | 0.9.5 | — | EOL | |
| 0.8 | Feb 19, 2013 | Mar 19, 2014 | Dec 31, 2015 | 3858d ago | 0.8.6 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
