PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-59739 Apache Software Foundation CVE debrief

Apache ZooKeeper's incomplete fix for CVE-2024-23944 allows information disclosure via SetWatches reconnect replay due to missing ACL checks. An attacker can discover ACL-restricted paths by registering exists-watches on non-existent paths and reconnecting after path creation with restricted ACLs. The issue exposes paths, not znode data, but paths may contain sensitive information like user names or login IDs, making this potentially critical.

Vendor
Apache Software Foundation
Product
Apache ZooKeeper
CVSS
HIGH 7.5
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-16
Original CVE updated
2026-09-18
Advisory published
2026-09-16
Advisory updated
2026-09-18

Who should care

ZooKeeper administrators and security teams should assess exposure and prioritize upgrading to a fixed version. Deployment contexts where sensitive path information could be at risk require immediate attention.

Why it matters

CVE-2026-59739 is a high-severity vulnerability in Apache ZooKeeper that allows information disclosure via SetWatches reconnect replay. It exposes ACL-restricted paths, potentially containing sensitive information like user names or login IDs. Defenders should assess exposure, especially in sensitive deployment contexts, and prioritize upgrading to version 3.9.6 or 3.8.7. Evidence is based on official CVE and NVD records, as well as a vendor advisory.

  • Path exposure in sensitive contexts could lead to unauthorized access or lateral movement
  • Potential for sensitive information disclosure through path names
  • Requires verification of current ACL configurations and inventory checks for exposure
  • Upgrade and remediation priority is high due to potential critical impact

Technical summary

The vulnerability in Apache ZooKeeper is due to an incomplete fix for CVE-2024-23944. The SetWatches/SetWatches2 reconnect replay handler, DataTree.setWatches(), calls watcher.process(event) with a null ACL, bypassing ACL checks entirely. This allows an attacker to discover ACL-restricted paths by registering exists-watches on non-existent paths and reconnecting after the paths are created with restricted ACLs.

Defensive priority

Upgrade to version 3.9.6 or 3.8.7 to fix the issue. Assess exposure in ZooKeeper deployments, especially where sensitive path information could be at risk.

Recommended defensive actions

  • Upgrade Apache ZooKeeper to version 3.9.6 or 3.8.7
  • Assess exposure in ZooKeeper deployments, especially where sensitive path information could be at risk
  • Review and adjust ACL configurations for sensitive paths
  • Verify current ACL configurations for potential exposure
  • Conduct inventory checks for systems that may be affected
  • Monitor for suspicious activity related to path exposure
  • Review change management processes for ZooKeeper updates

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and recommended actions. Vendor advisory from Apache is available via a mailing list. Evidence is based on official CVE and NVD records, as well as a vendor advisory. Defenders should verify current ACL configurations, inventory checks for exposure, and assess the potential impact of path exposure in sensitive contexts.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-59739 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-59739

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-59739 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-59739

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.