Quick answers
- Is CVE-2026-59969 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-59969 being exploited in the wild.
- How severe is CVE-2026-59969?
- High severity, with a CVSS score of 7.5, published 16 September 2026.
- Which products and versions are affected?
- Apache Zookeeper before 3.8.7, 3.9.x before 3.9.6.
- Is there a fix for CVE-2026-59969?
- A patch was published on 2026-09-16: Patches available in ZooKeeper 3.8.7 and 3.9.6 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-59969 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-59969?
- Check whether you run Apache Zookeeper at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This vulnerability is a certificate validation bypass in ZooKeeper's Java SSLSocket implementation for quorum communication. When sslQuorum=true, zookeeper.fips-mode=true, ssl.quorum.hostnameVerification=true, and ssl.quorum.clientHostnameVerification=true are all enabled, the code fails to properly enforce SAN matching during peer authentication. An attacker can present a certificate issued by a trusted CA that lacks SAN matching the target hostname and still be accepted into the cluster. Attack vectors include network position allowing connection to quorum members. The vulnerability enables unauthorized cluster membership, leader election tampering, and replication stream injection. Fixes are available in versions 3.8.7 and 3.9.6.
Affected products
- Apache ZooKeeper before 3.8.7, 3.9.x before 3.9.6
Timeline
- 2026-09-16: disclosed
- 2026-09-16: patched: Patches available in ZooKeeper 3.8.7 and 3.9.6