What runs on ZooKeeper / nifi
Does Apache NiFi use ZooKeeper?
Default for clustersA NiFi cluster elects its Cluster Coordinator and Primary Node through ZooKeeper, and NiFi can start an embedded ZooKeeper server so you do not run a separate ensemble. NiFi 2.x keeps ZooKeeper as the default but adds Kubernetes-based leader election and a ConfigMap state provider as alternatives.
Trusted globally by enterprises





What Apache NiFi uses ZooKeeper for
- Cluster Coordinator and Primary Node election.
- Cluster-wide state for processors (the ZooKeeper state provider).
Which ZooKeeper version ships with Apache NiFi
From the zookeeper.version property in pom.xml at each release tag. Many NiFi 1.x clusters run the embedded ZooKeeper (nifi.state.management.embedded.zookeeper.start=true).
| Release | ZooKeeper | ZooKeeper line status | Open ZooKeeper CVEs |
|---|---|---|---|
| NiFi 1.10.0 to 1.15.0 | 3.5.6 | End of life since 1 June 2022Bundles log4j 1.2.17 | 1 (CVE-2023-44981)2026 advisories not assessed for this line |
| NiFi 1.15.1 to 1.16.3 | 3.5.9 | End of life since 1 June 2022Bundles log4j 1.2.17 | 1 (CVE-2023-44981)2026 advisories not assessed for this line |
| NiFi 1.19.1 | 3.8.0 | Supported (latest 3.8.8) | 9 (CVE-2023-44981, CVE-2024-23944, CVE-2026-24281, CVE-2026-24308, CVE-2026-59739, CVE-2026-59969, CVE-2026-79993, CVE-2026-84439, CVE-2026-84501) |
| NiFi 1.28.1 | 3.9.3 | Supported (latest 3.9.7) | 8 (CVE-2025-58457, CVE-2026-24281, CVE-2026-24308, 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.5.6 is exposed to
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 NiFi is using
grep -E 'nifi.(zookeeper.connect.string|state.management.embedded.zookeeper.start|cluster.leader.election.implementation)' conf/nifi.properties
Can Apache NiFi run without ZooKeeper?
In NiFi 2.x on Kubernetes, yes: set the leader election implementation to KubernetesLeaderElectionManager and use the ConfigMap cluster state provider (subject to the 1 MB ConfigMap limit). NiFi 1.x clusters need ZooKeeper.
NiFi 1.28 is the last 1.x minor release, with end of support on 8 December 2024. NiFi 2.12.0 is current.
Your options
Upgrade to NiFi 2
A significant migration for flows that rely on components removed in 2.0, but it opens up Kubernetes-native clustering.
Keep NiFi 1.x, patched
OSSeva patches NiFi 1.x and its ZooKeeper, so dataflows stranded by the 2.0 rewrite stay supported.
Most teams buy this at the product level: keep the Apache NiFi estate supported, including the ZooKeeper under it. See Apache NiFi extended support.
ZooKeeper 3.5 custom support for NiFi 1.10 to 1.16
Which NiFi releases bundle ZooKeeper 3.5? NiFi 1.10 through 1.15.0 ship 3.5.6, and 1.15.1 through 1.16.3 ship 3.5.9. NiFi 1.17.0 moved to ZooKeeper 3.8.0.
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.
Many NiFi 1.x clusters run the embedded ZooKeeper, so the old jar sits inside the application rather than in a separate ensemble. Where moving NiFi to 1.17 or later is possible, that is the cleaner fix. Custom 3.5 support is for clusters that cannot move yet, and we scope the ZooKeeper build and the NiFi line together.
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 |
|---|---|
| NiFi 1.10.0 to 1.15.0 | 3.5.6 |
| NiFi 1.15.1 to 1.16.3 | 3.5.9 |
Source: nifi-nar-bundles/nifi-framework-bundle/pom.xml at each NiFi release tag (github.com/apache/nifi), checked 15 October 2026.
Can I run a NiFi cluster without ZooKeeper?
In NiFi 2.x on Kubernetes, yes, using Kubernetes leader election and the ConfigMap state provider. NiFi 1.x clusters require ZooKeeper, either embedded or external.
Get a quote
Keep Apache NiFi and the ZooKeeper under it supported.
Send us your versions; we reply with coverage, exposure and a plan within five working days.
Prefer to talk or read more first?