Apache ZooKeeper ACL bypass enables unauthorized znode deletion

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-79993?

CVE-2026-79993 is a vulnerability classified as Missing Authorization, affecting Apache ZooKeeper (affected versions: 3.9.0 – ≤ 3.9.5 and 3.8.0 – ≤ 3.8.6). This vulnerability is rated High, with a CVSS score of 7.5. Current sources do not report this vulnerability as exploited.

Overview

Original source data

The deleteContainer opcode (0x14/20) is processed without verifying the caller's ACL permissions, allowing any authenticated client to delete specific znodes in the data tree regardless of the ACL restrictions on the znode or its parent. This opcode is considered internal-only and the official client doesn't have API for it, but a client that can open a plain TCP session on the ZooKeeper client port (2181 by default) - with NO authentication and NO ACL permissions - can delete any empty persistent znode (including regular persistent nodes, container nodes, and TTL nodes) by issuing the raw protocol OpCode deleteContainer (20). The deleteContainer request path completely skips both the session check and the DELETE ACL check that are enforced by the regular delete (OpCode 2) path. This is an authorization bypass / ACL enforcement bug. This issue affects Apache ZooKeeper: from 3.9.0 through 3.9.5, from 3.8.0 through 3.8.6. Users are recommended to upgrade to version 3.9.6 or 3.8.7, which fixes the issue.

Affected products and scope

  • org.apache.zookeeper:zookeeper 3.9.0 through 3.9.5: affected.
  • org.apache.zookeeper:zookeeper 3.8.0 through 3.8.6: affected.
  • The advisory recommends upgrading the 3.9 branch to 3.9.6 or the 3.8 branch to 3.8.7.
  • The supplied evidence does not establish the status of parallel branches or releases outside these boundaries. Do not assume that every later release has been independently verified.

Technical details

Apache ZooKeeper processes the deleteContainer opcode without checking the caller's ACL permissions. This request path skips both the session check and the DELETE ACL check that are enforced by the regular delete path using opcode 2. A client that can open a plain TCP session to the ZooKeeper client port, 2181 by default, can send a raw protocol deleteContainer request to delete an empty persistent znode, including a regular persistent node, container node, or TTL node. The advisory states that this can be done with no authentication and no ACL permissions, so ACLs on the target znode or its parent do not prevent deletion through this path. The opcode is considered internal-only and the official client has no API for it, so an attacker needs a client or tool capable of constructing and sending the raw protocol request. The available evidence does not identify the exact source-level function or implementation detail changed by the fix.

Exploitability

The flaw is reachable over the network when an attacker can access the ZooKeeper client port. The evidence states that authentication, ACL permissions, and user interaction are not required; the attacker needs to construct a raw protocol request for the deleteContainer opcode. The official client does not expose an API for this opcode, so exploitation requires a client or tool that can open a TCP session and generate the appropriate protocol request. The supplied record does not identify a public exploit and does not establish observed exploitation status; that absence should not be treated as proof that exploitation has not occurred.

Technical impact

The direct technical result is that an attacker with network access to the client port can delete certain empty persistent znodes without the required DELETE permission. This creates unauthorized changes to the ZooKeeper data tree and could affect coordination or configuration state when applications depend on the deleted nodes. The impact is constrained by the requirement that the znode be empty, and the evidence does not describe data disclosure, code execution, or privilege escalation. Regular persistent nodes, container nodes, and TTL nodes are all included in the deletion types described by the advisory. The specific operational consequence depends on the role of each znode in the deployment.

Business impact

The flaw compromises the integrity of the ZooKeeper data tree by allowing empty znodes to be deleted regardless of the ACL on the znode or its parent.

  • Znodes used for coordination state, configuration state, or metadata could be removed without authorization if they are empty when the request is processed.
  • Removing state that an application expects to exist could cause abnormal operation or workflow interruption, depending on how that application uses the znode. This is a possible consequence, not a confirmed outcome for every deployment.
  • The evidence does not indicate data disclosure, and the described deletion scope is limited to empty persistent znodes, including regular persistent, container, and TTL nodes.
  • Existing ACLs do not protect the target from this request path; relying on ACLs alone is not a sufficient fix.

Remediation

  1. Upgrade org.apache.zookeeper:zookeeper to 3.9.6 for deployments on the 3.9 branch, or to 3.8.7 for deployments on the 3.8 branch. These are the specific fixed releases identified by the advisory.
  2. Inventory servers, clients, container images, and package caches to verify that the running process uses a fixed release, not merely that a dependency manifest was updated.
  3. Until the upgrade is complete, restrict access to the ZooKeeper client port, 2181 by default, to trusted clients and networks. This reduces reachability but does not correct the server-side defect.
  4. Do not rely on ACLs or authentication as the sole protection against this opcode, because the vulnerable request path skips both the session check and the DELETE ACL check.
  5. No other vendor-specific workaround is provided in the record. The status of release branches not explicitly covered by the advisory should be verified separately.

Detection

  1. Inventory all ZooKeeper deployments and the org.apache.zookeeper:zookeeper package, then compare the running versions with the affected branches.
  2. Identify exposed ZooKeeper client ports, especially listeners using the default port 2181 that are reachable from untrusted networks.
  3. If suitable protocol-level telemetry or audit data exists, review for deleteContainer requests and unexpected deletion of empty regular persistent, container, or TTL znodes. This is precautionary monitoring, not a vendor-confirmed indicator.
  4. Compare ZooKeeper audit records or data-tree snapshots for empty znodes deleted by callers that did not have the expected DELETE permission. The absence of log or audit evidence does not prove that an instance is safe.
  5. After upgrading, verify that the package and the running server processes use the fixed release rather than only updating a dependency manifest or repository artifact.
Sources (13)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.