Skip to main content
No exploitation reportedFix available

CVE-2026-59739

No exploitation reported by the sources we read.

  • Published2026-09-16
  • Fixed in3.9.6 · 3.8.7
  • WeaknessCWE-862

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Information disclosure via SetWatches reconnect replay in Apache ZooKeeper due to missing ACL check. An attacker can discover ACL-restricted paths by registering exists-watches on non-existent paths, then reconnecting after the paths are created with restricted ACLs. Issue is caused by incomplete fix for CVE-2024-23944 (ZOOKEEPER-4799). The fix added ACL checking to WatchManager.triggerWatch(). However, DataTree.setWatches() — the SetWatches/SetWatches2 reconnect replay handler — still calls watcher.process(event) with null ACL, bypassing the check entirely. It's important to note that only the path is exposed by this vulnerability, not the data of znode, but since znode path can contain sensitive information like user name or login ID, this issue is potentially critical. Users are recommended to upgrade to version 3.9.6, 3.8.7 which fixes the issue.

Timeline

dates in UTC
  1. 2026-09-1610:16CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2026-59739?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2026-59739?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · OSV
Apache zookeeper
BranchAffectedFixed in
3.9≥ 3.9.0, < 3.9.63.9.6
3.8≥ 3.8.0, < 3.8.73.8.7

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • CVE-2026-59739 Red Hat Product Security36 known affected

    zookeeper: Apache ZooKeeper: Information disclosure via SetWatches reconnect replay

    parent as a component of Red Hat AMQ Broker 7 · zookeeper as a component of Red Hat AMQ Broker 7 · zookeeper-jute as a component of Red Hat AMQ Broker 7 · +33 more

Full record on NVD

Fix

  1. Update Apache zookeeper to 3.9.6 · 3.8.7
  2. Workaround from the vendor Red Hat Product Security CVE-2026-59739 · 36 productsUpdate to Apache ZooKeeper 3.8.7, 3.9.6, or later.
  3. No fix available, says the vendor Red Hat Product Security CVE-2026-59739 · 36 productsFix deferred

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVE recordread 2026-10-23
  • CISA-ADPSSVC decisionnone2026-09-17
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.17.52026-09-17
  • CNAweakness (CWE)CWE-862read 2026-10-23
  • FIRST EPSSEPSS score0.6 %2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Published
2026-09-16
Last Modified
2026-09-18
NVD status
Analyzed

Frequently asked questions

What is CVE-2026-59739?

Information disclosure via SetWatches reconnect replay in Apache ZooKeeper due to missing ACL check. An attacker can discover ACL-restricted paths by registering exists-watches on non-existent paths, then reconnecting after the paths are created with restricted ACLs. Issue is caused by incomplete fix for CVE-2024-23944 (ZOOKEEPER-4799). The fix added ACL checking to WatchManager.triggerWatch(). However, DataTree.setWatches() — the SetWatches/SetWatches2 reconnect replay handler — still calls watcher.process(event) with null ACL, bypassing the check entirely. It's important to note that only the path is exposed by this vulnerability, not the data of znode, but since znode path can contain sensitive information like user name or login ID, this issue is potentially critical. Users are recommended to upgrade to version 3.9.6, 3.8.7 which fixes the issue.

Is CVE-2026-59739 actively exploited?

Active exploitation of CVE-2026-59739 has not been confirmed. Its EPSS score was 0.6% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-59739?

CVE-2026-59739 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.

Running zookeeper? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month