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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 0.8 | 0.8.6 | Feb 19, 2013 | Dec 31, 2015 | 3782 days past EOL | EOL |
| 0.9 | 0.9.5 | Mar 19, 2014 | Feb 28, 2016 | 3723 days past EOL | EOL |
| 0.10 | 0.10.5 | Feb 16, 2015 | Feb 28, 2017 | 3357 days past EOL | EOL |
| 0.11 | 0.11.3 | Jul 12, 2015 | Aug 1, 2017 | 3203 days past EOL | EOL |
| 0.12 | 0.12.1 | Feb 23, 2016 | Feb 28, 2018 | 2992 days past EOL | EOL |
| 0.13 | 0.13.2 | Aug 23, 2016 | Aug 1, 2018 | 2838 days past EOL | EOL |
| 0.14 | 0.14.3 | Mar 8, 2017 | Feb 1, 2019 | 2654 days past EOL | EOL |
| 0.15 | 0.15.2 | Sep 15, 2017 | Aug 1, 2019 | 2473 days past EOL | EOL |
| 0.16 | 0.16.3 | Feb 26, 2018 | Feb 1, 2020 | 2289 days past EOL | EOL |
| 0.17 | 0.17.2 | Oct 3, 2018 | Aug 1, 2020 | 2107 days past EOL | EOL |
| 0.18 | 0.18.1 | May 2, 2019 | Feb 1, 2021 | 1923 days past EOL | EOL |
| 0.19 | 0.19.2 | Nov 24, 2019 | Aug 1, 2021 | 1742 days past EOL | EOL |
| 0.20 | 0.20.2 | Jun 3, 2020 | Feb 1, 2022 | 1558 days past EOL | EOL |
| 0.21 | 0.21.2 | Jan 15, 2021 | Oct 1, 2022 | 1316 days past EOL | EOL |
| 22 | 22.1 | Sep 13, 2021 | Apr 1, 2023 | 1134 days past EOL | EOL |
| 23 | 23.2 | Apr 25, 2022 | Dec 1, 2023 | 890 days past EOL | EOL |
| 24 | 24.2 | Nov 24, 2022 | Apr 2, 2024 | 767 days past EOL | EOL |
| 25 | 25.2 | May 18, 2023 | Oct 2, 2024 | 584 days past EOL | EOL |
| 26 | 26.2 | Dec 6, 2023 | Apr 14, 2025 | 390 days past EOL | EOL |
| 27 | 27.2 | Apr 16, 2024 | Oct 10, 2025 | 211 days past EOL | EOL |
| 28 | 28.4 | Oct 2, 2024 | Apr 19, 2026 | 20 days past EOL | EOL |
| 29 | 29.3 | Apr 14, 2025 | Already EOL | Supported | Active |
| 30 | 30.2 | Oct 10, 2025 | Already EOL | Supported | Active |
| 31 | 31.0 | Apr 19, 2026 | Already EOL | Supported | Active |
When a Bitcoin Core 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 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →