Complete end-of-life dates, support windows, and security status for all Hbase versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2.2 | 2.2.7 | Jul 25, 2019 | Apr 19, 2021 | 1846 days past EOL | EOL |
| 1.7 | 1.7.2 | Jun 12, 2021 | Aug 9, 2022 | 1369 days past EOL | EOL |
| 2.3 | 2.3.7 | Jul 13, 2020 | Oct 19, 2021 | 1663 days past EOL | EOL |
| 2.4 | 2.4.18 | Dec 15, 2020 | May 25, 2025 | 349 days past EOL | EOL |
| 2.5 | 2.5.14 | Aug 31, 2022 | Already EOL | Supported | Active |
| 2.6 | 2.6.5 | May 17, 2024 | Already EOL | Supported | Active |
When a Hbase 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 Hbase 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 →