NVD / CVE Program· CNA apache

CVE-2026-79993: Apache ZooKeeper: Missing ACL check on deleteContainer opcode allows unauthorized deletion of any empty persistent/container znode

HighCVSS 7.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.60% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
According to CISA the attack is automatable: targets can be found by mass scanning.
Fixed version: Apache Software Foundation Apache ZooKeeper 3.9.6.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Apache Software Foundation Apache ZooKeeper 3.9.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

EUVD-2026-80332

Published: Sep 16, 2026
Updated: Sep 18, 2026
EPSS: 0.6% · 49th percentile
CWE: CWE-862

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 30 / 40 · 7.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.6%

CISA SSVC decision

Exploitation: none
Automatable: yes
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
apache	zookeeper	cpe:2.3:a:apache:zookeeper

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

Apache Software Foundation Apache ZooKeeper
- 3.9.0 and later · up to and including 3.9.5affected · maven
- 3.8.0 and later · up to and including 3.8.6affected · maven

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

apache zookeeper3.8.0 and later · before 3.8.7
apache zookeeper3.9.0 and later · before 3.9.6

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Debian:12	zookeeper	from 0	—
Debian:14	zookeeper	before 3.9.6-1	3.9.6-1

Same product

apache: all records

Other highest-scoring records for the same primary product.

CVE-2017-5637Two four letter word commands "wchp/wchc" are CPU intensive and could cause spike of CPU utilization on Apache ZooKeeper server if abused…
52Plan
CVE-2023-44981Apache ZooKeeper: Authorization bypass in SASL Quorum Peer Authentication
37Monitor
CVE-2024-51504Apache ZooKeeper: Authentication bypass with IP-based authentication in Admin Server
36Monitor

Published before and after this one in the same product

← EarlierCVE-2026-59739Sep 16, 2026 · Apache ZooKeeper: Information disclosure via SetWatches reconnect replay
30Monitor
← EarlierCVE-2026-59969Sep 16, 2026 · Apache ZooKeeper: Improper validation of certificate with host mismatch in FIPS mode
30Monitor
Later →CVE-2026-84439Sep 16, 2026 · Apache ZooKeeper: Audit log injection via unsanitized output from multiple sources
21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Apache Software Foundation Apache ZooKeeper	3.9.6 · description	Vendor (CNA)
debian:zookeeper	3.9.6-1 · Debian:14	Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.