OSSEVA FOR APACHE HBASE
HBase 2.4 is end of life. Your HBase support does not have to be.
OSSeva provides HBase support for HBase 1.7, 2.2 to 2.6 and 3.0, including patched builds for 1.7, 2.2, 2.3 and 2.4 after the HBase project stopped fixing them. The final 2.4 release, 2.4.18, shipped on 25 May 2024, and HBase 1.x ended with 1.7.2 in August 2022. The ZooKeeper they run on is patched in the same build.
Reply within 1 business day ยท No commitment ยท or book a 15-minute call
Which vendors provide patched Apache HBase after end of life? HBase 2.4 and 1.x After End of Life.
Last reviewed
Trusted globally by enterprises





Why now
Only 2.5, 2.6 and 3.0 still get fixes
The HBase reference guide lists 2.5 and 2.6 as the active release lines, and 3.0.0 shipped on 5 August 2026. Everything older is end of maintenance: 2.4 since its last release, 2.4.18, in May 2024, 1.x since August 2022, 2.3 since October 2021 and 2.2 since April 2021. HBase clusters sit under long-lived applications, so the installed base runs well behind that line.
The hidden ZooKeeper time bomb
Every distributed HBase cluster depends on ZooKeeper, and HBase 3.0 still needs it on the server side. HBase 1.7.2 and 2.2.7 bundle ZooKeeper 3.4.10, from a line that reached end of life on 1 June 2020 and is exposed to CVE-2019-0201. HBase 2.3.7 bundles 3.5.7, which still ships log4j 1.2.17. When HBase manages its own ensemble, that bundled version is the server running in production. Few teams have ever checked it.
An HBase upgrade is rarely just HBase
The reference guide keeps a separate Hadoop compatibility matrix for each HBase line and recommends Hadoop 3. A cluster on HBase 1.x or 2.2 usually sits on Hadoop 2, so the HBase upgrade turns into a Hadoop upgrade. Inside a CDH or HDP cluster it turns into a platform migration. Patched builds keep the cluster supported while that decision is made.
Versions covered
All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.
| Version | Status | Active CVEs |
|---|---|---|
| 1.7.x(Community EOL Aug 2022 โ OSSeva patched) | EOL | Clean |
| 2.2.x(Community EOL Apr 2021 โ OSSeva patched) | EOL | Clean |
| 2.3.x(Community EOL Oct 2021 โ OSSeva patched) | EOL | Clean |
| 2.4.x(Community EOL 25 May 2024 โ OSSeva patched) | EOL | Clean |
| 2.5.x(Upstream maintained) | Extended | Clean |
| 2.6.x(Upstream maintained) | Extended | Clean |
| 3.0.x(Released 5 Aug 2026) | Current | Clean |
Running a Apache HBase version or build not listed here?
What you get
Three tiers โ pick the level of engagement that matches your team's operational needs and compliance requirements.
OSSeva Patch
Patched, signed HBase 1.7, 2.2, 2.3 and 2.4 builds, bundled ZooKeeper included.
- Security backports for 1.7, 2.2, 2.3 and 2.4, region data untouched
- Bundled ZooKeeper patched in the same build
- Transitive dependency patching (Netty, Jetty, Jackson, log4j)
- Maven / Docker / tarball delivery
- Signed artifacts (GPG) and VEX statements for scanner findings
- Cluster and ensemble security audit
- 24/7 managed operations
OSSeva Assure
Patch plus a cluster audit covering HBase, Hadoop and ZooKeeper together.
- Everything in Patch
- Master, region server and ZooKeeper quorum review
- Kerberos, ACL and coprocessor exposure audit
- Hadoop and ZooKeeper version map for every HBase cluster
- SOC 2 / HIPAA attestation package with VEX for auditors
- Upgrade plan to 2.5, 2.6 or 3.0
- 24/7 reactive support
OSSeva Operate
Full MSP: 24/7 HBase monitoring, 15-min SLA, named engineers.
- Everything in Assure
- 24/7 region, compaction and RPC latency monitoring
- 15-minute P1 incident response SLA
- Named senior HBase engineer
- Region balancing, snapshot and replication management
- Rolling upgrade execution with the ZooKeeper quorum preserved
- Quarterly capacity and hotspot reviews
All tiers priced per cluster/application โ not per core.
How it installs
OSSeva artifacts arrive via your existing package infrastructure. Pull the patched version the same way you pull upstream today โ just from the OSSeva registry.
# HBase version on this node
hbase version 2>/dev/null | head -1
# ZooKeeper jar bundled with this HBase
ls $HBASE_HOME/lib/ | grep -E '^zookeeper-[0-9]'
# Is HBase running its own ensemble from that jar?
grep HBASE_MANAGES_ZK $HBASE_HOME/conf/hbase-env.sh
# Version the ensemble is actually running
echo srvr | nc zk1.internal 2181 | head -1<dependency>
<groupId>io.osseva.hbase</groupId>
<artifactId>hbase-shaded-client</artifactId>
<version>2.4.18-osseva-1</version>
</dependency>Migrate from Unsupported HBase 1.x and 2.4 clusters
OSSeva ships patched builds on the HBase line you already run, so region layout, coprocessors and client jars stay as they are, and the bundled ZooKeeper is patched in the same build. When the cluster moves to 2.5, 2.6 or 3.0, OSSeva plans and runs the rolling upgrade with the Hadoop and ZooKeeper layers kept in step.
Pricing model
OSSeva for Apache HBase is priced per cluster, not per region server or per table.
ZooKeeper 3.5 custom support for HBase 2.3 to 2.5
Which HBase releases bundle ZooKeeper 3.5? HBase 2.3, 2.4.0 through 2.4.17, and 2.5.0 through 2.5.6 bundle ZooKeeper 3.5.7. HBase 2.4.18 and 2.5.7 onwards moved to the 3.8 line.
ZooKeeper 3.5 reached end of life on 1 June 2022, and 3.5.10 was its last release, so the Apache project issues no more fixes for it. OSSeva's standard ZooKeeper coverage starts at 3.6. ZooKeeper 3.5 is offered as custom support, scoped per engagement.
Custom support covers CVE backports into 3.5.x builds made from the upstream source, and SBOM and VEX evidence for each build. A scanner finding or an auditor's question then gets a written answer for your configuration: fixed, not present, or not reachable.
HBase masters and region servers need ZooKeeper in every release, including 3.0, so the ensemble cannot be dropped while the cluster waits for its own upgrade. We scope the ZooKeeper 3.5 build with the HBase line you run.
Send us the versions you run and we scope it with you. Contact us for a quote.
Releases that bundle ZooKeeper 3.5.x
| Release | Bundled ZooKeeper |
|---|---|
| HBase 2.3.0 to 2.3.7, 2.4.0 to 2.4.17 and 2.5.0 to 2.5.6 | 3.5.7 |
Source: zookeeper.version in pom.xml at each HBase release tag (github.com/apache/hbase), checked 15 October 2026.
Compliance library
Is HBase 2.4 end of life?
Yes. HBase 2.4.18, released on 25 May 2024, was announced as the last patch release of the 2.4 line. The reference guide lists 2.5 and 2.6 as the active lines, and 3.0.0 was released on 5 August 2026.
When did HBase 1.x reach end of life?
HBase 1.7.2, released on 9 August 2022, was the last release of the 1.x line, and the HBase reference guide lists 1.7 as end of life from August 2022. HBase 1.7.2 bundles ZooKeeper 3.4.10.
Does HBase 3.0 still need ZooKeeper?
Yes, on the server side. HBase 3.0 makes RpcConnectionRegistry the default for clients, so applications no longer need ZooKeeper to find hbase:meta, but masters and region servers still coordinate through it. The work to remove ZooKeeper from client connections is targeted at HBase 4.
Which ZooKeeper version does my HBase bundle?
It depends on the release. HBase 1.7.2 and 2.2.7 bundle ZooKeeper 3.4.10, 2.3.7 bundles 3.5.7, 2.4.18 bundles 3.8.4, and 2.5.16, 2.6.7 and 3.0.0 bundle 3.8.6. The 3.4 and 3.5 lines are past community end of life. OSSeva patches the bundled ZooKeeper together with HBase; ZooKeeper 3.5, bundled in 2.3 and parts of 2.4 and 2.5, is custom support scoped per engagement.
Can OSSeva patch HBase without an upgrade?
Yes. OSSeva ships patched builds on 1.7, 2.2, 2.3 and 2.4, so the region layout, table schemas, coprocessors and client jars stay as they are. Patched builds go in through a normal rolling restart. Start with Patch, and talk to an engineer when the move to 2.5, 2.6 or 3.0 is on the table.
Who provides HBase support besides the Apache HBase project?
Cloudera is the commercial vendor for HBase inside its CDH and HDP distributions, cloud providers offer managed HBase services, and third-party support companies are a third option. OSSeva fits where the cluster has to stay as it is: one contract across the stack, end-of-life HBase lines included, and support that runs wherever you run HBase. The ZooKeeper under HBase is patched in the same build.
Does OSSeva support current HBase versions or only end-of-life ones?
Both. The versions list covers HBase 1.7, 2.2 to 2.6 and 3.0, with patches active on every line. Patch ships signed builds for 1.7, 2.2, 2.3 and 2.4, and Assure plans the upgrade to 2.5, 2.6 or 3.0. OSSeva Operate patches Critical CVEs (CVSS โฅ 9.0) within 48 hours and High within 7 days.
How is OSSeva HBase support priced?
OSSeva for Apache HBase is priced per cluster, not per region server or per table. Patch covers signed patched builds, Assure adds the cluster audit and upgrade plan with 24/7 reactive support, and Operate adds proactive 24/7 monitoring and end-to-end managed operations with a 15-minute P1 SLA. Book a discovery call for a quote.
Get a quote
Ready to get Apache HBase patched and supported?
Tell us your Apache HBase versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.
Prefer to talk or read more first?