Bamboo End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Bamboo versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 8.0 | 8.0.13 | Jul 29, 2021 | Mar 28, 2023 | 1183 days past EOL | EOL |
| 8.1 | 8.1.12 | Dec 14, 2021 | Mar 28, 2023 | 1183 days past EOL | EOL |
| 8.2 | 8.2.9 | Apr 9, 2022 | May 15, 2023 | 1135 days past EOL | EOL |
| 9.0 | 9.0.4 | Aug 25, 2022 | May 16, 2023 | 1134 days past EOL | EOL |
| 9.1 | 9.1.3 | Dec 14, 2022 | Jun 15, 2023 | 1104 days past EOL | EOL |
| 9.2 LTS | 9.2.24 | Feb 7, 2023 | Mar 4, 2025 | 476 days past EOL | EOL |
| 9.3 | 9.3.6 | Jun 1, 2023 | Jun 1, 2025 | 387 days past EOL | EOL |
| 9.4 | 9.4.4 | Oct 26, 2023 | Oct 26, 2025 | 240 days past EOL | EOL |
| 9.5 | 9.5.4 | Jan 22, 2024 | Jan 22, 2026 | 152 days past EOL | EOL |
| 9.6 LTS | 9.6.27 | Mar 13, 2024 | Mar 14, 2026 | 101 days past EOL | EOL |
| 10.0 | 10.0.3 | Aug 21, 2024 | Aug 21, 2026 | 59 days remaining | Warning |
| 10.1 | 10.1.1 | Nov 19, 2024 | Nov 20, 2026 | 150 days remaining | Warning |
| 10.2 LTS | 10.2.20 | Dec 19, 2024 | Dec 20, 2026 | 180 days remaining | Active |
| 11.0 | 11.0.8 | Apr 29, 2025 | Apr 30, 2027 | 311 days remaining | Active |
| 12.0 | 12.0.2 | Nov 20, 2025 | Nov 20, 2027 | 515 days remaining | Active |
| 12.1 LTS | 12.1.8 | Dec 16, 2025 | Dec 17, 2027 | 542 days remaining | Active |
What does Bamboo end of life mean for your organization?
When a version of Bamboo 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 Bamboo 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Bamboo versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →