Missing Authorization Affecting zookeeper-3.9 package, versions <3.9.6-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-MINIMOSLATEST-ZOOKEEPER39-19958133
- published20 Sept 2026
- disclosed16 Sept 2026
Introduced: 16 Sep 2026
NewCVE-2026-79993 (opens in a new tab)How to fix?
Upgrade Minimos:latest zookeeper-3.9 to version 3.9.6-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream zookeeper-3.9 package and not the zookeeper-3.9 package as distributed by Minimos.
See How to fix? for Minimos:latest relevant fixed versions and status.
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.
References
- https://www.cve.org/CVERecord?id=CVE-2026-79993
- https://github.com/advisories/GHSA-9x9g-5r48-3wvg
- https://osv.dev/vulnerability/MINI-835h-854j-wh9h
- https://osv.dev/vulnerability/CVE-2026-79993
- https://lists.apache.org/thread/9cw3rmrzhqpct26v8j18fy41bghlq8y5
- http://www.openwall.com/lists/oss-security/2026/09/15/5