CriticalGHSA-7286-pgfv-vxvhBIT-zookeeper-2023-44981CVE-2023-44981

Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper

Published 11 Oct 2023 · Updated 10 Sept 2026

Is your project on an affected org.apache.zookeeper:zookeeper?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
<3.7.2
Fixed in
3.7.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.zookeeper:zookeeper -DdepVersion=3.7.2 -DforceVersion=true
Affected
>=3.8.0 <3.8.3
Fixed in
3.8.3
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.zookeeper:zookeeper -DdepVersion=3.8.3 -DforceVersion=true
Affected
>=3.9.0 <3.9.1
Fixed in
3.9.1
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.zookeeper:zookeeper -DdepVersion=3.9.1 -DforceVersion=true

Details

Authorization Bypass Through User-Controlled Key vulnerability in Apache ZooKeeper. If SASL Quorum Peer authentication is enabled in ZooKeeper (quorum.auth.enableSasl=true), the authorization is done by verifying that the instance part in SASL authentication ID is listed in zoo.cfg server list. The instance part in SASL auth ID is optional and if it's missing, like 'eve@EXAMPLE.COM', the authorization check will be skipped. As a result an arbitrary endpoint could join the cluster and begin propagating counterfeit changes to the leader, essentially giving it complete read-write access to the data tree. Quorum Peer authentication is not enabled by default.

Users are recommended to upgrade to version 3.9.1, 3.8.3, 3.7.2, which fixes the issue.

Alternately ensure the ensemble election/quorum communication is protected by a firewall as this will mitigate the issue.

See the documentation for more details on correct cluster administration.

Is GHSA-7286-pgfv-vxvh in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.zookeeper:zookeeper, and gives you the command that fixes it.

More advisories for org.apache.zookeeper:zookeeper

  • HighCVE-2026-24281Apache ZooKeeper: Reverse-DNS fallback enables hostname verification bypass in ZooKeeper ZKTrustManager · 7 Mar 2026
  • HighCVE-2026-24308Apache ZooKeeper has improper handling of configuration values · 7 Mar 2026
  • MediumCVE-2025-58457Apache ZooKeeper: Insufficient Permission Check in AdminServer Snapshot/Restore Commands · 24 Sept 2025
  • HighCVE-2024-51504Apache ZooKeeper: Authentication bypass with IP-based authentication in Admin Server · 7 Nov 2024
  • MediumCVE-2024-23944Apache ZooKeeper vulnerable to information disclosure in persistent watchers handling · 15 Mar 2024
  • HighCVE-2017-5637Uncontrolled Resource Consumption in Apache ZooKeeper · 13 May 2022
All 9 advisories for org.apache.zookeeper:zookeeper

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.