CVE-2026-115448 · Package
NO FIX YET · SEE WHAT TO DO
ZooKeeper's snapshot code recurses once per znode level with no depth limit, so a client that can create nested znodes can build a tree that exhausts the JVM stack. The same tree is rebuilt from the transaction log on restart, so the server keeps failing and can lose data during recovery.
first public Nov 4, 2026 · 1 source
Is this in your stack? Find out in 2 minutes.
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
Any deployment running ZooKeeper 3.8.0 through 3.8.7 or 3.9.0 through 3.9.6 where clients can create znodes, which is the default because the root ACL is open. Ensembles are affected together because the leader and followers replay the same log. Deployments that already restrict znode creation with ACLs and authentication are less exposed.
Not affected if auth-required, patched-version, restricted-root-acl
Who cares hadoop, hbase, kafka, self-hosted, zookeeper
zkServer.sh version and compare it to the affected ranges 3.8.0 through 3.8.7 and 3.9.0 through 3.9.6.zkCli.sh getAcl /.3.8.8 for the 3.8 line3.9.7 for the 3.9 lineUncontrolled recursion in Apache ZooKeeper. The server serializes its data tree to a snapshot by recursing one stack frame per znode level, with no depth bound. A client permitted to create znodes (the default root ACL is open) can build a chain of nested znodes deep enough that taking a snapshot exhausts the JVM stack and kills the snapshot thread; sizes stay within jute.maxbuffer, so existing limits do not prevent it. This is a denial of service that becomes persistent: on restart the server rebuilds the deep tree from its transaction log and fails again while taking the startup snapshot, so it does not return to service, and recovery can entail data loss. The same log affects a leader and its followers, so it can spread across an ensemble.
This issue affects Apache ZooKeeper 3.8.0 through 3.8.7 and 3.9.0 through 3.9.6. Users are recommended to upgrade to 3.8.8 or 3.9.7, which fix the issue. As a workaround, use ACLs and authentication to restrict znode creation rather than relying on the default open root ACL.
This page as .md · .json · in your agent: get_signal("CVE-2026-115448") · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.