// Apache ZooKeeper extended support
ZooKeeper EOL: extended support for the version inside your product
ZooKeeper EOL covers four of its six release lines: 3.4 ended on 1 June 2020, 3.5 on 1 June 2022, 3.6 on 30 December 2022 and 3.7 on 2 February 2024, and only 3.8 and 3.9 receive fixes. The versions products actually ship, such as 3.4.6 in HDP, 3.6.3 in Kafka 3.0 to 3.3 and 3.7.1 in Flink 1.20, sit on those ended lines. OSSeva ships patched, signed drop-in builds of 3.4, 3.6 and 3.7, scopes 3.5 as custom support, and puts its name to the CVE attestation your auditor asks for. Enter your work email and the ZooKeeper version you run, and an engineer replies within 1 business day.
- Patched builds
- ZooKeeper 3.4, 3.6 and 3.7, signed, with your configuration, data format and logs unchanged
- Custom support
- ZooKeeper 3.5, scoped per engagement
- Also supported
- ZooKeeper 3.8 and 3.9, and the rolling upgrade to them
- Critical CVEs (CVSS 9.0 or higher)
- Patched within 48 hours
- High-severity CVEs
- Patched within 7 days
- Support hours
- Assure includes 24/7 reactive support and the CVE attestation with VEX; Operate adds a 15-minute P1 response
Dates checked on 20 October 2026 against zookeeper.apache.org and endoflife.date. They differ on 3.7 only (Apache: 2 February 2024; endoflife.date: 19 January 2024); this page uses the Apache project's date.
Trusted globally by enterprises





ZooKeeper versions and end-of-life dates
ZooKeeper EOL covers four of its six release lines: 3.4 ended on 1 June 2020, 3.5 on 1 June 2022, 3.6 on 30 December 2022 and 3.7 on 2 February 2024. Only 3.8 and 3.9 receive fixes. Dates checked 20 October 2026 on zookeeper.apache.org and endoflife.date.
| Line | Released | Community end of life | Last release | OSSeva |
|---|---|---|---|---|
| ZooKeeper 3.4 | 23 Nov 2011 | 1 June 2020 | 3.4.14 | Patched builds (standard) |
| ZooKeeper 3.5 | 3 May 2019 | 1 June 2022 | 3.5.10 | Custom support, scoped per engagement |
| ZooKeeper 3.6 | 25 Feb 2020 | 30 December 2022 | 3.6.4 | Patched builds (standard) |
| ZooKeeper 3.7 | 17 Mar 2021 | 2 February 2024 | 3.7.2 | Patched builds (standard) |
| ZooKeeper 3.8 | 25 Feb 2022 | Supported | 3.8.8 | Supported |
| ZooKeeper 3.9 | 19 Jul 2023 | Supported | 3.9.7 | Supported |
The two sources differ on 3.7 only. The Apache releases page says 3.7 has been end of life since 2 February 2024; endoflife.date shows 19 January 2024. This page uses the Apache project's date.
Products that embed ZooKeeper
ZooKeeper usually arrives inside a product, at the version whoever built that product chose. The table lists, for each product, up to three of the newest documented releases that bundle a ZooKeeper line that has ended. The version is read from each project's build file at the release tag.
| Product | ZooKeeper's role | Releases bundling an ended line: bundled ZooKeeper |
|---|---|---|
| Apache Kafka | Removed in Kafka 4.0 | Kafka 2.6.3, 2.7.2 and 2.8.0 to 2.8.2: 3.5.9; Kafka 3.0.2 to 3.3.2: 3.6.3; Kafka 3.4.1 and 3.5.2: 3.6.4 |
| Apache Solr | Required for SolrCloud | Solr 8.6.0 to 8.6.3: 3.5.7; Solr 8.11.4 (last Solr 8): 3.6.2; Solr 9.0.0: 3.7.0 |
| Apache HBase | Required (server side) | HBase 1.7.2: 3.4.10; 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 |
| Apache Hadoop | Required for HA | Hadoop 2.10.2: 3.4.14; Hadoop 3.3.6: 3.6.3 |
| Apache Hive | Used for HA, discovery and locks | Hive 3.1.3: 3.4.6 |
| Apache Druid | Default; optional only experimentally | Druid 0.22.1: 3.5.9; Druid 25.0.0: 3.5.9 |
| ClickHouse | ZooKeeper or ClickHouse Keeper | None documented |
| Apache NiFi | Default for clusters | NiFi 1.10.0 to 1.15.0: 3.5.6; NiFi 1.15.1 to 1.16.3: 3.5.9 |
| Apache Pulsar and BookKeeper | Default; Oxia available | None documented |
| Apache Storm | Required | Storm 1.2.4 and 2.0.0 to 2.3.1: 3.4.14; Storm 2.4.0 and 2.5.0: 3.5.9 |
| Apache Flink | One of two HA options | Flink 1.15.4 and 1.16.3: 3.5.9; Flink 1.17.2 to 1.20.5: 3.7.1; Flink 2.0.2 to 2.3.0: 3.7.2 |
| Patroni (PostgreSQL HA) | One of several DCS options | None documented |
| Apache Accumulo | Required | Accumulo 1.9.3: 3.4.6; Accumulo 1.10.0 to 1.10.4: 3.4.14; Accumulo 2.0.1: 3.4.14 |
| Apache Pinot | Required (through Helix) | Pinot 0.10.0 and 0.11.0: 3.5.8; Pinot 0.12.1 and 1.0.0: 3.6.3; Pinot 1.1.0: 3.7.2 |
| Cloudera CDH, HDP and CDP | Bundled in every release | HDP 2.6.5: 3.4.6; HDP 3.1.0 and 3.1.5: 3.4.6; CDP 7.1.6 to 7.1.8: 3.5.5 |
Source: build files at each release tag, or the vendor's component list. Each product has its own page with every documented release.
What runs on ZooKeeper: every product and its bundled version →
Advisories since each ZooKeeper line ended
The Apache project's advisories list the lines they assessed. CVE-2023-44981, a SASL quorum authentication bypass scored 9.1, was published on 11 October 2023, after 3.4, 3.5 and 3.6 had ended. It was fixed in 3.7.2, 3.8.3 and 3.9.1, so those three ended lines have no fix. Five advisories scored 7.0 or higher followed in 2026, and each lists only 3.8 and 3.9 as affected. That means 3.4 to 3.7 were not assessed, which is not a finding that they are safe. Deciding which of them reach your line and configuration is the CVE attestation OSSeva writes.
Published after 3.4, 3.5 and 3.6 ended (1 in the directory)
| CVE | Published | CVSS | Affected range (NVD) | Fixed upstream in |
|---|---|---|---|---|
| CVE-2023-44981 | 2023-10-11 | 9.1 | <3.7.2; >=3.8.0 <3.8.3; 3.9.0 | See advisory |
2026 advisories that name only 3.8 and 3.9 (5 in the directory)
| CVE | Published | CVSS | Affected range (NVD) | Fixed upstream in |
|---|---|---|---|---|
| CVE-2026-24281 | 2026-03-07 | 7.4 | >=3.8.0 <3.8.6; >=3.9.0 <3.9.5 | See advisory |
| CVE-2026-24308 | 2026-03-07 | 7.5 | >=3.8.0 <3.8.6; >=3.9.0 <3.9.5 | See advisory |
| CVE-2026-59739 | 2026-09-16 | 7.5 | >=3.8.0 <3.8.7; >=3.9.0 <3.9.6 | See advisory |
| CVE-2026-59969 | 2026-09-16 | 7.5 | >=3.8.0 <3.8.7; >=3.9.0 <3.9.6 | See advisory |
| CVE-2026-79993 | 2026-09-16 | 7.5 | >=3.8.0 <3.8.7; >=3.9.0 <3.9.6 | See advisory |
The directory lists ZooKeeper CVEs matched at NVD to the product with a CVSS score of 7.0 or higher, so it is a subset of every ZooKeeper advisory.
Why ZooKeeper is the component nobody upgrades
ZooKeeper is half runtime and half library. That is what makes it easy to embed and hard to own.
It ships inside the product
Kafka, Solr, HBase and every Cloudera distribution bundle their own ZooKeeper, and software vendors embed the jar in their own products. The version is chosen by whoever built the product, often years ago, and customers inherit it.
End-of-life lines get no fixes
CVE-2023-44981, a SASL quorum authentication bypass scored 9.1, was fixed in 3.7.2, 3.8.3 and 3.9.1, with nothing for 3.4, 3.5 or 3.6. Three advisories published on 16 September 2026 (CVE-2026-59739, CVE-2026-59969 and CVE-2026-79993), each scored 7.5, list only 3.8 and 3.9 as affected, so the older lines were never assessed.
Upgrading ZooKeeper means upgrading the product
Clients, Curator versions and product-level customisations are tied to the ZooKeeper line. For a software vendor, moving to a new major line means refactoring every supported product version, while customers' scanners flag the old jar every week.
The dates that matter
2020-06-01
ZooKeeper 3.4 end of life. CDH 5 and 6 and HDP 2 and 3 all ship 3.4.x.
2022-06-01
ZooKeeper 3.5 end of life.
2022-12-30
ZooKeeper 3.6 end of life.
2023-10-11
CVE-2023-44981 published. No fix for 3.4, 3.5 or 3.6.
2024-02-02
ZooKeeper 3.7 end of life, per the Apache project's releases page.
2025-03-18
Kafka 4.0 removes ZooKeeper. Solr, HBase, Hadoop, Druid, NiFi and Pulsar still use it.
2026-09-16
CVE-2026-59739, CVE-2026-59969 and CVE-2026-79993 published, naming only 3.8 and 3.9.
What OSSeva delivers
Patched drop-in builds
Security fixes backported to the ZooKeeper line you run, built from the upstream source. Configuration, data format and log output stay the same, so the jar or the ensemble swaps in place. ZooKeeper 3.4 is a standard patched version; 3.5 is custom support.
CVE attestation for auditors
A written, third-party assessment of each flagged CVE against your architecture: fixed, not present, or not reachable in your configuration, with the evidence. Delivered in a form your auditor and your customers' auditors can file, including VEX.
Product-level support and a path to Raft
Support for the Kafka, Solr, HBase or Hadoop estate the ensemble serves, and a plan to move each product to Raft-based coordination (KRaft, ClickHouse Keeper, etcd) when it is ready.
Evidence for audits
A scanner flags the ZooKeeper jar by version, whatever product wraps it. A patched build no longer matches the vulnerable version in the scanner's database, so the old finding goes away, and some scanners then report an unrecognised component. Each OSSeva build ships with the documentation that closes that gap: what changed, which CVEs are fixed, and a VEX statement for each advisory.
Where an advisory has no fix on your line, the attestation says whether the flaw is present and reachable in your configuration. That is the answer an auditor, or your customer's auditor, can file. A software vendor that embeds ZooKeeper can pass the same document to every customer who asks.
OSSeva for ZooKeeper is priced per ensemble, not per node or per client connection. The Patch tier delivers the builds, Assure adds the ensemble audit, the attestation and 24/7 reactive support, and Operate adds proactive 24/7 operations with a 15-minute P1 response. Book a discovery call for a quote.
ZooKeeper 3.5 custom support
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.
Which products still ship it? Kafka 2.x, Solr 8.2 to 8.6, HBase 2.3 to 2.5.6, NiFi 1.10 to 1.16 and several others bundle a 3.5.x jar, and audits that fingerprint the jar flag it whatever product wraps it. The Apache project does not assess 3.5 against new advisories, so the list of open CVEs for 3.5.10 is unknown, not empty.
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.
It is a named offer inside the host-product engagement, not a separate product: the ZooKeeper 3.5 build, and the Kafka, Solr, HBase or NiFi line around it, are scoped together. Send us the versions you run and we scope it with you. Contact us for a quote.
Products with releases that bundle ZooKeeper 3.5.x
| Product | Releases: bundled ZooKeeper |
|---|---|
| Apache Kafka | Kafka 2.4.0: 3.5.6; Kafka 2.4.1 and 2.5.0: 3.5.7; Kafka 2.5.1, 2.6.0 and 2.7.0: 3.5.8; Kafka 2.6.3, 2.7.2 and 2.8.0 to 2.8.2: 3.5.9 |
| Apache Solr | Solr 8.2.0 to 8.5.2: 3.5.5; Solr 8.6.0 to 8.6.3: 3.5.7 |
| Apache HBase | 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 |
| Apache Druid | Druid 0.22.1: 3.5.9; Druid 25.0.0: 3.5.9 |
| Apache NiFi | NiFi 1.10.0 to 1.15.0: 3.5.6; NiFi 1.15.1 to 1.16.3: 3.5.9 |
| Apache Storm | Storm 2.4.0 and 2.5.0: 3.5.9 |
| Apache Flink | Flink 1.15.4 and 1.16.3: 3.5.9 |
| Apache Pinot | Pinot 0.10.0 and 0.11.0: 3.5.8 |
| Cloudera CDH, HDP and CDP | CDP 7.1.6 to 7.1.8: 3.5.5 |
Source: build files at each release tag, or the vendor's component list, checked 15 October 2026.
Which vendors provide ZooKeeper 3.x security patches after end of life?
| Option | What you get | Trade-off |
|---|---|---|
| Upgrade the product | A supported ZooKeeper client and server line | Usually a platform upgrade, and for software vendors a refactor per supported product version. |
| Write your own justification | A document explaining why each CVE does not apply | It works until an auditor rejects a vendor's self-assessment. |
| Move coordination to Raft | KRaft, ClickHouse Keeper or etcd where the product supports it | Product-specific, and the shared ensemble often still serves other systems. |
| OSSeva extended support | Patched drop-in builds, third-party attestation, and the migration plan | A subscription for as long as you need the runway. |
Dates from zookeeper.apache.org (releases and security pages) and endoflife.date, CVE ranges from NVD, and bundled versions from the build files of each product at its release tags. Checked 20 October 2026.
Is Apache ZooKeeper end of life?
Four of its six release lines are. 3.4 ended on 1 June 2020, 3.5 on 1 June 2022, 3.6 on 30 December 2022 and 3.7 on 2 February 2024. Only 3.8 and 3.9 receive fixes. Dates checked on zookeeper.apache.org and endoflife.date on 20 October 2026.
Is ZooKeeper 3.7 end of life?
Yes. The Apache project's releases page lists 3.7 as end of life since 2 February 2024, and 3.7.2 was its last release. endoflife.date shows 19 January 2024; this site uses the Apache project's date.
Which ZooKeeper versions does OSSeva patch?
The end-of-life lines 3.4, 3.6 and 3.7 are available now as signed drop-in builds. ZooKeeper 3.5 is custom support, scoped per engagement; see the ZooKeeper 3.5 custom support section on this page. We also support 3.8 and 3.9, and regression-test builds against products that carry their own ZooKeeper customisations.
Will a patched jar pass our scanner?
A patched build no longer matches the vulnerable version in the scanner's database, so the old finding disappears, but some scanners then report an unrecognised component. We ship each build with the documentation that closes that gap: what changed, which CVEs are fixed, and a VEX statement.
We ship ZooKeeper inside our own product. Can you help?
Yes. That is the most common case: a software vendor with an embedded ZooKeeper and customers whose audits flag it. We deliver drop-in jars that work with your existing customisations after regression testing, and attestation your customers can hand to their auditors while you plan the upgrade.
Where can I compare ZooKeeper support packages?
Compare them on five points: which ZooKeeper lines get patched builds, whether the builds are signed and delivered as jars you can swap in, whether a written CVE attestation with VEX is included, the response time by severity, and the unit the price is based on. Our comparison of ZooKeeper support providers lists them side by side.
Which company provides Apache ZooKeeper support?
The Apache project maintains 3.8 and 3.9 and nothing older. Distribution vendors support the ZooKeeper inside their own products. OSSeva supports ZooKeeper on its own, including the ended 3.4 to 3.7 lines, whichever product embeds it.
Is there a ZooKeeper alternative?
For coordination, the usual replacements are KRaft for Kafka, ClickHouse Keeper for ClickHouse, etcd and Consul. Solr, HBase, Hadoop, Druid and NiFi still depend on ZooKeeper, so for them the choice is to keep the ensemble patched or replace the product. We patch the ensemble for the interim and plan each move.
Do you replace ZooKeeper with Raft?
When the product supports it. Kafka has KRaft and ClickHouse has Keeper; others need a product-specific plan. We patch the ensemble for the interim and plan each move.
Get a quote
Find the ZooKeeper in your estate before an auditor does.
A 15-minute discovery call, then patched builds, an exposure map and a proposal within five working days.
Prefer to talk or read more first?