Couchbase Server End of Life Dates
other
Couchbase Server, a source-available, distributed multi-model NoSQL document-oriented database software package, has been a staple in the development community since its inception as Membase. Originally created to cater to the needs of interactive applications, this software has been actively maintained and updated to ensure seamless performance and security. With a strong focus on optimization, Couchbase Server has garnered a significant following among developers who require a robust and reliable database solution. The fact that it is source-available has also contributed to its widespread adoption, as developers can modify and customize the software to suit their specific needs.
The end-of-life landscape for Couchbase Server is characterized by a total of 22 versions, out of which 19 have already reached their end-of-life. Currently, only 3 versions remain active, with the latest stable version being 8.0.1. As the software continues to evolve, developers need to stay informed about upcoming end-of-life dates to ensure they can plan and migrate to newer versions accordingly. The next version slated to reach its end-of-life is 7.2, which is set to expire on July 31, 2026. This information is crucial for developers who are still using this version, as they will need to upgrade to a newer version to continue receiving support and security updates.
From a security standpoint, Couchbase Server presents a relatively clean slate, with a total of 0 CVEs tracked and 0 critical vulnerabilities. As a result, there is no most affected version, and the software is not listed on the Known Exploited Vulnerabilities catalog. This is a testament to the software's robust security framework and the dedication of its maintainers to ensuring the integrity of the software. Given this security picture, developers can continue to use Couchbase Server with confidence, but it is still essential to stay up-to-date with the latest versions and security patches to minimize any potential risks. By doing so, developers can ensure the continued security and reliability of their applications.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 8.0 | Oct 21, 2025 | — | Oct 31, 2028 | in 739d | 8.0.3 | — | Active | |
| 7.6 | Mar 25, 2024 | — | Mar 31, 2027 | in 159d | 7.6.12 | — | Active | |
| 7.2 | Jun 1, 2023 | — | Jul 31, 2026 | 84d ago | 7.2.9 | — | EOL | |
| 7.1 | May 10, 2022 | — | Jan 31, 2024 | 996d ago | 7.1.6 | — | EOL | |
| 7.0 | Jul 29, 2021 | — | Jan 31, 2023 | 1361d ago | 7.0.5 | — | EOL | |
| 6.6 | Aug 12, 2020 | — | Jan 31, 2023 | 1361d ago | 6.6.6 | — | EOL | |
| 6.5 | Jan 21, 2020 | — | Feb 28, 2021 | 2063d ago | 6.5.2 | — | EOL | |
| 6.0 | Oct 31, 2018 | — | Jul 31, 2020 | 2275d ago | 6.0.5 | — | EOL | |
| 5.5 | Jul 23, 2018 | — | Jul 31, 2020 | 2275d ago | 5.5.6 | — | EOL | |
| 5.1 | Feb 28, 2018 | — | Jan 31, 2019 | 2822d ago | 5.1.3 | — | EOL | |
| 5.0 | Oct 26, 2017 | — | Aug 31, 2018 | 2975d ago | 5.0.1 | — | EOL | |
| 4.6 | Feb 16, 2017 | — | Aug 31, 2018 | 2975d ago | 5.0.1 | — | EOL | |
| 4.5 | Jun 27, 2016 | — | Apr 30, 2018 | 3098d ago | 4.5.1 | — | EOL | |
| 4.1 | Dec 10, 2015 | — | Apr 30, 2018 | 3098d ago | 4.1.2 | — | EOL | |
| 4.0 | Oct 6, 2015 | — | Apr 30, 2017 | 3463d ago | 4.0.0 | — | EOL | |
| 3.1 | Aug 31, 2015 | — | Feb 28, 2017 | 3524d ago | 3.1.3 | — | EOL | |
| 3.0 | Dec 17, 2014 | — | Apr 30, 2016 | 3828d ago | 3.0.3 | — | EOL | |
| 2.5 | Feb 28, 2014 | — | Dec 31, 2015 | 3949d ago | 2.5.0 | — | EOL | |
| 2.2 | Sep 30, 2013 | — | Mar 31, 2015 | 4224d ago | 2.2.0 | — | EOL | |
| 2.1 | Jun 26, 2013 | — | Dec 31, 2014 | 4314d ago | 2.1.0 | — | EOL | |
| 2.0 | Dec 31, 2012 | — | Jun 30, 2014 | 4498d ago | 2.0.0 | — | EOL | |
| 1.8 | Jul 31, 2012 | — | Jan 31, 2014 | 4648d ago | 1.8.0 | — | EOL |
Data sourced from endoflife.date · CVE data from NVD
