Bitbucket End of Life Dates
other
Developers rely on Bitbucket, a Git-based source code repository hosting service, to manage their codebases efficiently. Owned by Atlassian, Bitbucket has been a staple in the development community since its inception, providing both commercial plans and free accounts with an unlimited number of private repositories. With a strong focus on collaboration and version control, Bitbucket has become an essential tool for teams of all sizes. The Atlassian team continuously maintains and updates Bitbucket to ensure it meets the evolving needs of developers, which is why it remains a popular choice among professionals.
The end-of-life landscape for Bitbucket is characterized by a total of 25 versions, with 14 of these versions having already reached their end-of-life. Currently, 11 versions remain active, with the latest stable version being 10.0.2. Looking ahead, version 9.0 is slated to reach its end-of-life on 2026-07-23, marking an important milestone for developers who still rely on this version. Recently, version 8.19 met its end-of-life on 2026-03-12, underscoring the importance of staying up-to-date with the latest versions of Bitbucket.
Given the current security landscape, Bitbucket has a spotless record with 0 total CVEs tracked and 0 critical CVEs. As a result, there is no most affected version, and no Known Exploited Vulnerabilities status applies. This pristine security record is a testament to the dedication of the Atlassian team in ensuring the integrity of Bitbucket. Developers can continue to use Bitbucket with confidence, but it is still essential to stay informed about upcoming end-of-life dates and plan accordingly to avoid any potential disruptions to their workflows. By doing so, they can maintain the security and stability of their codebases.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 10.4 | May 12, 2026 | — | Jul 21, 2028 | in 683d | 10.4.2 | — | Active | |
| 10.3 | May 12, 2026 | — | May 12, 2028 | in 613d | 10.3.2 | — | Active | |
| 10.2 LTS | Mar 3, 2026 | — | Mar 3, 2028 | in 543d | 10.2.6 | — | Active | |
| 10.1 | Nov 20, 2025 | — | Nov 20, 2027 | in 439d | 10.1.5 | — | Active | |
| 10.0 | Sep 7, 2025 | — | Sep 8, 2027 | in 366d | 10.0.2 | — | Active | |
| 9.6 | Mar 17, 2025 | — | Jan 18, 2027 | in 133d | 9.6.5 | — | Active | |
| 9.5 | Jan 7, 2025 | — | Jan 7, 2027 | in 122d | 9.5.2 | — | Active | |
| 9.4 LTS | Dec 2, 2024 | — | Dec 3, 2026 | in 87d | 9.4.23 | — | EOL soon | |
| 9.3 | Oct 29, 2024 | — | Oct 29, 2026 | in 52d | 9.3.2 | — | EOL soon | |
| 9.2 | Sep 24, 2024 | — | Sep 24, 2026 | in 17d | 9.2.1 | — | EOL soon | |
| 9.1 | Aug 27, 2024 | — | Aug 27, 2026 | 11d ago | 9.1.1 | — | EOL | |
| 9.0 | Jul 23, 2024 | — | Jul 23, 2026 | 46d ago | 9.0.1 | — | EOL | |
| 8.19 LTS | Mar 12, 2024 | — | Mar 12, 2026 | 179d ago | 8.19.29 | — | EOL | |
| 8.18 | Feb 6, 2024 | — | Feb 6, 2026 | 213d ago | 8.18.1 | — | EOL | |
| 8.17 | Jan 9, 2024 | — | Jan 9, 2026 | 241d ago | 8.17.2 | — | EOL | |
| 8.16 | Nov 28, 2023 | — | Nov 28, 2025 | 283d ago | 8.16.4 | — | EOL | |
| 8.15 | Oct 23, 2023 | — | Oct 24, 2025 | 318d ago | 8.15.5 | — | EOL | |
| 8.14 | Sep 19, 2023 | — | Sep 19, 2025 | 353d ago | 8.14.6 | — | EOL | |
| 8.13 | Aug 14, 2023 | — | Aug 15, 2025 | 388d ago | 8.13.6 | — | EOL | |
| 8.12 | Jul 11, 2023 | — | Jul 11, 2025 | 423d ago | 8.12.6 | — | EOL | |
| 8.11 | Jun 6, 2023 | — | Jun 6, 2025 | 458d ago | 8.11.6 | — | EOL | |
| 8.10 | May 1, 2023 | — | May 2, 2025 | 493d ago | 8.10.6 | — | EOL | |
| 8.9 LTS | Apr 12, 2023 | — | Apr 12, 2025 | 513d ago | 8.9.27 | — | EOL | |
| 8.8 | Feb 6, 2023 | — | Feb 7, 2025 | 577d ago | 8.8.7 | — | EOL | |
| 8.7 | Jan 10, 2023 | — | Jan 10, 2025 | 605d ago | 8.7.5 | — | EOL | |
| 7.21 LTS | Feb 28, 2022 | — | Feb 28, 2024 | 922d ago | 7.21.23 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
