Apache ZooKeeper: ACL enforcement bypass allows unauthorized operations to commit after an ACL revocation
Affects zookeeperSource GCVE Database
Not known to be exploited · CVSS 6.0 Medium : upgrade to 3.9.7 or 3.8.8 when convenient.
Data as of 17 Nov 2026, 16:06 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 4.0 | 6.0 |
|---|
- Patch
- Available – fixed in 3.9.7, 3.8.8
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 4 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
Upgrade zookeeper to 3.9.7 or 3.8.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Bitnamizookeeperpkg:bitnami/zookeeperOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Users should upgrade Apache ZooKeeper to version 3.8.8 or 3.9.7 or later, where this race condition in ACL enforcement has been fixed. No other specific mitigations are indicated. Applying the official patch is the recommended remediation.
Description
Apache ZooKeeper contains a time-of-check to time-of-use (TOCTOU) race condition in its setACL request handling that allows unauthorized operations to be committed after an ACL revocation. During the window between submitting a setACL request and its commit, operations are authorized against the old ACL but applied after the ACL change, enabling clients to perform actions they should no longer have permission for. This affects versions prior to 3.8.8 and between 3.9.0 and before 3.9.7. Upgrading to 3.8.8 or 3.9.7 resolves the issue.