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: Sep 7, 2026

VersionReleasedActive supportEOL dateUntil EOLLatestCVEsStatusAlert me
31 Apr 19, 2026Apr 20, 2026No31.1Active
30 Oct 10, 2025Oct 10, 2025No30.3Active
29 Apr 14, 2025Oct 10, 2025No29.4Active
28 Oct 2, 2024Oct 10, 2025Apr 19, 2026141d ago28.4EOL
27 Apr 16, 2024Apr 14, 2025Oct 10, 2025332d ago27.2EOL
26 Dec 6, 2023Oct 2, 2024Apr 14, 2025511d ago26.2EOL
25 May 18, 2023Apr 16, 2024Oct 2, 2024705d ago25.2EOL
24 Nov 24, 2022Dec 12, 2023Apr 2, 2024888d ago24.2EOL
23 Apr 25, 2022May 18, 2023Dec 1, 20231011d ago23.2EOL
22 Sep 13, 2021Dec 14, 2022Apr 1, 20231255d ago22.1EOL
0.21 Jan 15, 2021Apr 25, 2022Oct 1, 20221437d ago0.21.2EOL
0.20 Jun 3, 2020Sep 13, 2021Feb 1, 20221679d ago0.20.2EOL
0.19 Nov 24, 2019Jan 15, 2021Aug 1, 20211863d ago0.19.2EOL
0.18 May 2, 2019Jun 3, 2020Feb 1, 20212044d ago0.18.1EOL
0.17 Oct 3, 2018Nov 24, 2019Aug 1, 20202228d ago0.17.2EOL
0.16 Feb 26, 2018May 2, 2019Feb 1, 20202410d ago0.16.3EOL
0.15 Sep 15, 2017Oct 3, 2018Aug 1, 20192594d ago0.15.2EOL
0.14 Mar 8, 2017Feb 26, 2018Feb 1, 20192775d ago0.14.3EOL
0.13 Aug 23, 2016Sep 15, 2017Aug 1, 20182959d ago0.13.2EOL
0.12 Feb 23, 2016Mar 31, 2017Feb 28, 20183113d ago0.12.1EOL
0.11 Jul 12, 2015Aug 23, 2016Aug 1, 20173324d ago0.11.3EOL
0.10 Feb 16, 2015Feb 29, 2016Feb 28, 20173478d ago0.10.5EOL
0.9 Mar 19, 2014Jun 16, 2015Feb 28, 20163844d ago0.9.5EOL
0.8 Feb 19, 2013Mar 19, 2014Dec 31, 20153903d ago0.8.6EOL

Data sourced from endoflife.date · CVE data from NVD

Related technologies

Frequently Asked Questions