Apache ZooKeeper: Unbounded recursion
Affects zookeeperSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 3.9.7 or 3.8.8 soon.
Data as of 17 Nov 2026, 16:05 UTC
Thin evidence
One scorer or none| CNA (apache) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 3.9.7, 3.8.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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
Upgrade Apache ZooKeeper to version 3.8.8 or 3.9.7 or later, where this issue is fixed. As a workaround, restrict znode creation permissions using ACLs and authentication to prevent untrusted clients from creating deeply nested znodes. Do not rely on the default open root ACL for security.
Description
Apache ZooKeeper versions 3.8.0 through 3.8.7 and 3.9.0 through 3.9.6 contain a vulnerability where unbounded recursion during snapshot serialization can exhaust the JVM stack. A client with permission to create znodes can craft a deeply nested znode structure that causes the server's snapshot thread to crash, resulting in a denial of service. This denial of service is persistent because the server fails to recover on restart due to the same deep tree being rebuilt from the transaction log, potentially causing data loss. The issue can propagate across an ensemble affecting leader and follower nodes. Fixed in versions 3.8.8 and 3.9.7.