Apache ZooKeeper: Information disclosure via SetWatches reconnect replay
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-59739
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 23:56 UTC · Revision 1
Source evidence
Apache ZooKeeper: Information disclosure via SetWatches reconnect replay
core-osv · Original sourcePublished 16 Sept 2026, 09:26 UTC
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.
osv:CVE-2026-59739
Complete source record
{
"id": "2c61621d7f6faf0995fecbae5894d6e73c957c05e2e6cb2505d0949774ddd120",
"url": "https://osv.dev/vulnerability/CVE-2026-59739",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Apache ZooKeeper: Information disclosure via SetWatches reconnect replay",
"summary": "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.",
"evidence": "osv:CVE-2026-59739",
"products": [],
"severity": "high",
"structured": {
"id": "CVE-2026-59739",
"aliases": [
"BIT-zookeeper-2026-59739",
"CVE-2026-59739"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/apache/zookeeper",
"type": "GIT",
"events": [
{
"introduced": "97c181a40d6dd6ccb2fdad7fcdbd1fd74ab0b6c8"
},
{
"fixed": "9085db92dd679e1e90a63bfe6ae6345ab6cbc4ae"
},
{
"introduced": "1674a5e97f43bc38e9bf56b04f83a7ae34d68249"
},
{
"fixed": "a355171b081b5b60749db8f19cca1528b0df936f"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:apache:zookeeper:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.8.0"
},
{
"fixed": "3.8.7"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:apache:zookeeper:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.9.0"
},
{
"fixed": "3.9.6"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"release-3.9.5-0",
"release-3.9.5",
"release-3.9.4-2",
"release-3.9.4",
"release-3.9.4-1",
"release-3.9.4-0",
"release-3.9.3-2",
"release-3.9.3",
"release-3.9.3-1",
"release-3.9.3-0",
"release-3.9.2-0",
"release-3.9.2",
"release-3.9.1-0",
"release-3.9.1",
"release-3.9.0-1",
"release-3.9.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-59739.json"
}
}
],
"modified": "2026-10-28T02:30:40.422582372Z",
"provider": "osv",
"references": [
"https://repo.maven.apache.org/maven2",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/59xxx/CVE-2026-59739.json",
"https://lists.apache.org/thread/v0lrwsbdxvx6w67p3z7fxf3hzyncq55l",
"https://nvd.nist.gov/vuln/detail/CVE-2026-59739"
],
"provider_metadata": {
"cwe_ids": [
"CWE-862"
],
"cna_assigner": "apache",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "3.9.0"
},
{
"last_affected": "3.9.5"
},
{
"introduced": "3.8.0"
},
{
"last_affected": "3.8.6"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/59xxx/CVE-2026-59739.json"
}
},
"related_cves": [
{
"value": "CVE-2026-59739",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 508189,
"published_at": "2026-09-16T09:26:37.69+00:00"
}