Zookeeper vulnerabilitiesRanked by how likely they are to be used.
Zookeeper is made by Apache. We track 7 published vulnerabilities in it, across 100 versions. None of them is on the list of flaws known to be exploited today. If you run Zookeeper, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Zookeeper vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Zookeeper's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Zookeeper flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 73%CVE-2017-5637High
Two four letter word commands "wchp/wchc" are CPU intensive and could cause spike of CPU utilization on Apache ZooKeeper server if abused, which leads to the server unable to serve legitimate client requests.
- 9.7%CVE-2019-0201Medium
An issue is present in Apache ZooKeeper 1.0.0 to 3.4.13 and 3.5.0-alpha to 3.5.4-beta.
- 8.5%CVE-2018-8012High
No authentication/authorization is enforced when a server attempts to join a quorum in Apache ZooKeeper before 3.4.10, and 3.5.0-alpha through 3.5.3-beta.
- 7.9%CVE-2016-5017High
Buffer overflow in the C cli shell in Apache Zookeeper before 3.4.9 and 3.5.x before 3.5.3, when using the "cmd:" batch mode syntax, allows attackers to have unspecified impact via a long command string.
- 2.2%CVE-2023-44981Critical
Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper.
- 0.3%CVE-2025-58457Medium
Improper permission check in ZooKeeper AdminServer lets authorized clients to run snapshot and restore command with insufficient permissions.
Running Zookeeper? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
Two four letter word commands "wchp/wchc" are CPU intensive and could cause spike of CPU utilization on Apache ZooKeeper server if abused, which leads to the server unable to serve legitimate client requests. Apache ZooKeeper thru version 3.4.9 and 3.5.2 suffer from this issue, fixed in 3.4.10, 3.5.3, and later.
- Matched to
- Zookeeper on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 7 published vulnerabilities listed under the name Zookeeper, across 100 versions.
None of Zookeeper's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Zookeeper. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.