Is org.apache.zookeeper:zookeeper 3.4 vulnerable?
Maven · 15 releases from 3.4.0 to 3.4.14 · latest org.apache.zookeeper:zookeeper is 3.9.7 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. org.apache.zookeeper:zookeeper 3.4.14, the last 3.4 release, is affected by 1 known security advisory (1 critical), including CVE-2023-44981. 3 more affect earlier 3.4.x releases. Upgrade to 3.7.2 or later to fix all of them.
mvn versions:use-dep-version -Dincludes=org.apache.zookeeper:zookeeper -DdepVersion=3.7.2 -DforceVersion=trueIs your project on an affected org.apache.zookeeper:zookeeper?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting org.apache.zookeeper:zookeeper 3.4.14
Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper
- Affected
- <3.7.2 · >=3.8.0 <3.8.3 · >=3.9.0 <3.9.1
- Fixed in
- 3.7.2, 3.8.3, 3.9.1
Fixed within 3.4.x, affecting earlier releases
Uncontrolled Resource Consumption in Apache ZooKeeper
- Affected
- >=3.4.0 <3.4.10 · >=3.5.0 <3.5.3
- Fixed in
- 3.4.10, 3.5.3
Missing Authorization in Apache ZooKeeper
- Affected
- <3.4.10 · >=3.5.0-alpha <3.5.4-beta
- Fixed in
- 3.4.10, 3.5.4-beta
Access control bypass in Apache ZooKeeper
- Affected
- >=1.0.0 <3.4.14 · >=3.5.0 <3.5.5
- Fixed in
- 3.4.14, 3.5.5
Every org.apache.zookeeper:zookeeper 3.4.x release
Affected: 3.4.0 to 3.4.14. Latest org.apache.zookeeper:zookeeper: 3.9.7.
| Version | Known advisories |
|---|---|
| org.apache.zookeeper:zookeeper 3.4.14 | CVE-2023-44981 |
| org.apache.zookeeper:zookeeper 3.4.13 | CVE-2023-44981, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.12 | CVE-2023-44981, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.11 | CVE-2023-44981, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.10 | CVE-2023-44981, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.9 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.8 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.7 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.6 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.5 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.4 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.3 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.2 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.1 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
| org.apache.zookeeper:zookeeper 3.4.0 | CVE-2023-44981, CVE-2017-5637, CVE-2018-8012, CVE-2019-0201 |
Which of your client projects are still on org.apache.zookeeper:zookeeper 3.4?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.zookeeper:zookeeper version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other org.apache.zookeeper:zookeeper versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.