What runs on ZooKeeper / hbase

Does Apache HBase use ZooKeeper?

Required (server side)

Yes. A distributed HBase install depends on a running ZooKeeper ensemble, which HBase can manage itself or use externally. HBase 3.0 moved the client connection registry off ZooKeeper by default, but the servers still require it, and the issue to remove ZooKeeper from client connections is targeted at HBase 4.

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

What Apache HBase uses ZooKeeper for

  • Master election and region server tracking.
  • Cluster coordination state and table state transitions.
  • Client bootstrap in older releases: clients found hbase:meta through ZooKeeper. HBase 2.5 added RpcConnectionRegistry, which is the default in 3.0.

Which ZooKeeper version ships with Apache HBase

From the zookeeper.version property in the root pom.xml at each release tag. Set HBASE_MANAGES_ZK=false to run an external ensemble.

ReleaseZooKeeperZooKeeper line statusOpen ZooKeeper CVEs
HBase 1.7.23.4.10End of life since 1 June 2020Bundles log4j 1.2.172 (CVE-2019-0201, CVE-2023-44981)2026 advisories not assessed for this line
HBase 2.3.0 to 2.3.7, 2.4.0 to 2.4.17 and 2.5.0 to 2.5.63.5.7End of life since 1 June 2022Bundles log4j 1.2.171 (CVE-2023-44981)2026 advisories not assessed for this line
HBase 2.4.183.8.4Supported (latest 3.8.8)7 (CVE-2026-24281, CVE-2026-24308, CVE-2026-59739, CVE-2026-59969, CVE-2026-79993, CVE-2026-84439, CVE-2026-84501)
HBase 2.5.16, 2.6.7 and 3.0.03.8.6Supported (latest 3.8.8)5 (CVE-2026-59739, CVE-2026-59969, CVE-2026-79993, CVE-2026-84439, CVE-2026-84501)

CVE counts are ZooKeeper's own advisories matched against the upstream version. The Apache ZooKeeper project does not assess end-of-life lines against new advisories, so "not assessed" means unknown, not safe.

What ZooKeeper 3.4.10 is exposed to

CVE-2019-0201 · CVSS 5.9 · fixed in 3.4.14, 3.5.5

getACL() performs no permission check and exposes unsalted digest authentication hashes.

CVE-2023-44981 · CVSS 9.1 · fixed in 3.7.2, 3.8.3, 3.9.1

SASL quorum peer authentication bypass, giving full read-write access to the data tree. Applies when quorum.auth.enableSasl=true.

Find the ZooKeeper HBase is using

# Bundled client jar
ls lib/ | grep -E '^zookeeper-[0-9]'

# Is HBase managing its own ensemble?
grep HBASE_MANAGES_ZK conf/hbase-env.sh

# Ensemble address
grep -A1 hbase.zookeeper.quorum conf/hbase-site.xml

Can Apache HBase run without ZooKeeper?

No. HBase 3.0 reduced what clients need from ZooKeeper, but region servers and masters still coordinate through it. Work to reduce the dependency further is open for HBase 4.

HBase 2.5 and 2.6 are the active lines, and 3.0.0 shipped in August 2026. The reference guide marks 2.4 and everything older as end of maintenance.

Your options

Upgrade HBase

Move to 2.5 or 2.6, which bundle ZooKeeper 3.8.6. For estates inside a Cloudera or Hortonworks distribution, the HBase upgrade usually means a platform upgrade.

Patch in place

OSSeva ships patched HBase builds for 1.x and 2.4 and patches the ZooKeeper ensemble under them, so an HBase 1.x or 2.4 cluster behind a legacy application stays supported while the platform decision is made.

Most teams buy this at the product level: keep the Apache HBase estate supported, including the ZooKeeper under it. See HBase extended support.

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

ReleaseBundled ZooKeeper
HBase 2.3.0 to 2.3.7, 2.4.0 to 2.4.17 and 2.5.0 to 2.5.63.5.7

Source: zookeeper.version in pom.xml at each HBase release tag (github.com/apache/hbase), checked 15 October 2026.

Get a quote for ZooKeeper 3.5 support

Questions

Frequently asked questions

Book a 15-minute call

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 depend on it.

Which ZooKeeper version does HBase 1.7 use?

HBase 1.7.2 bundles ZooKeeper 3.4.10. The 3.4 line reached end of life on 1 June 2020.

Should HBase manage its own ZooKeeper?

For production, most teams run an external ensemble (HBASE_MANAGES_ZK=false) so ZooKeeper can be upgraded and monitored independently of HBase restarts.

Get a quote

Keep Apache HBase and the ZooKeeper under it supported.

Send us your versions; we reply with coverage, exposure and a plan within five working days.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call