Bitcoin Core End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Bitcoin Core versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Bitcoin Core 31 is supported, with no end-of-life or end-of-support date announced yet. 21 of 24 tracked Bitcoin Core versions are past end of life; the most recent to reach it, 28, did so on April 19, 2026. The full Bitcoin Core lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.8 | 0.8.6 | Feb 19, 2013 | Dec 31, 2015 | 3919 days past EOL | EOL |
| 0.9 | 0.9.5 | Mar 19, 2014 | Feb 28, 2016 | 3860 days past EOL | EOL |
| 0.10 | 0.10.5 | Feb 16, 2015 | Feb 28, 2017 | 3494 days past EOL | EOL |
| 0.11 | 0.11.3 | Jul 12, 2015 | Aug 1, 2017 | 3340 days past EOL | EOL |
| 0.12 | 0.12.1 | Feb 23, 2016 | Feb 28, 2018 | 3129 days past EOL | EOL |
| 0.13 | 0.13.2 | Aug 23, 2016 | Aug 1, 2018 | 2975 days past EOL | EOL |
| 0.14 | 0.14.3 | Mar 8, 2017 | Feb 1, 2019 | 2791 days past EOL | EOL |
| 0.15 | 0.15.2 | Sep 15, 2017 | Aug 1, 2019 | 2610 days past EOL | EOL |
| 0.16 | 0.16.3 | Feb 26, 2018 | Feb 1, 2020 | 2426 days past EOL | EOL |
| 0.17 | 0.17.2 | Oct 3, 2018 | Aug 1, 2020 | 2244 days past EOL | EOL |
| 0.18 | 0.18.1 | May 2, 2019 | Feb 1, 2021 | 2060 days past EOL | EOL |
| 0.19 | 0.19.2 | Nov 24, 2019 | Aug 1, 2021 | 1879 days past EOL | EOL |
| 0.20 | 0.20.2 | Jun 3, 2020 | Feb 1, 2022 | 1695 days past EOL | EOL |
| 0.21 | 0.21.2 | Jan 15, 2021 | Oct 1, 2022 | 1453 days past EOL | EOL |
| 22 | 22.1 | Sep 13, 2021 | Apr 1, 2023 | 1271 days past EOL | EOL |
| 23 | 23.2 | Apr 25, 2022 | Dec 1, 2023 | 1027 days past EOL | EOL |
| 24 | 24.2 | Nov 24, 2022 | Apr 2, 2024 | 904 days past EOL | EOL |
| 25 | 25.2 | May 18, 2023 | Oct 2, 2024 | 721 days past EOL | EOL |
| 26 | 26.2 | Dec 6, 2023 | Apr 14, 2025 | 527 days past EOL | EOL |
| 27 | 27.2 | Apr 16, 2024 | Oct 10, 2025 | 348 days past EOL | EOL |
| 28 | 28.4 | Oct 2, 2024 | Apr 19, 2026 | 157 days past EOL | EOL |
| 29 | 29.4 | Apr 14, 2025 | TBD | Supported | Active |
| 30 | 30.3 | Oct 10, 2025 | TBD | Supported | Active |
| 31 | 31.1 | Apr 19, 2026 | TBD | Supported | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/bitcoin-core)
Bitcoin Core release and support pattern
Across the 24 release lines with a published release date, Bitcoin Core has shipped a new line roughly every 6 months (median interval). A line typically stays supported for about 1.8 years from its release to its end-of-life date (measured on the 21 lines with both dates published).
Of the 24 release lines tracked, 21 are past end of life and 3 are still within support. The newest line, 31, was released April 19, 2026. No end-of-life date is currently published for the 3 supported lines.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Bitcoin Core end of life mean for your organization?
When a version of Bitcoin Core 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Bitcoin Core 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.
Your options when Bitcoin Core reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Bitcoin Core versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Bitcoin Core has 21 versions past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Bitcoin Core is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."