CVE-2026-59739 Vulnerability Analysis & Exploit Details

CVE-2026-59739
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2026-59739 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-59739 Details

Status: Analyzed

Last updated: 🕝 18 Sep 2026, 14:37 UTC
Originally published on: 🕙 16 Sep 2026, 10:16 UTC

Time between publication and last update: 2 days

CVSS Release: version 3

CVSS3 Source

134c704f-9b21-4f2e-91b3-4a467353bcc0

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

CVE-2026-59739 Vulnerability Summary

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.

Assessing the Risk of CVE-2026-59739

Access Complexity Graph

The exploitability of CVE-2026-59739 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-59739

With low attack complexity and no required privileges, CVE-2026-59739 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-59739, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-59739, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2026-59739 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: None
    CVE-2026-59739 poses no threat to data integrity.
  • Availability: None
    CVE-2026-59739 does not impact system availability.

CVE-2026-59739 References

External References

CWE Common Weakness Enumeration

CWE-862

CAPEC Common Attack Pattern Enumeration and Classification

  • Exploitation of Thunderbolt Protection Flaws CAPEC-665 An adversary leverages a firmware weakness within the Thunderbolt protocol, on a computing device to manipulate Thunderbolt controller firmware in order to exploit vulnerabilities in the implementation of authorization and verification schemes within Thunderbolt protection mechanisms. Upon gaining physical access to a target device, the adversary conducts high-level firmware manipulation of the victim Thunderbolt controller SPI (Serial Peripheral Interface) flash, through the use of a SPI Programing device and an external Thunderbolt device, typically as the target device is booting up. If successful, this allows the adversary to modify memory, subvert authentication mechanisms, spoof identities and content, and extract data and memory from the target device. Currently 7 major vulnerabilities exist within Thunderbolt protocol with 9 attack vectors as noted in the Execution Flow.

Vulnerable Configurations

  • cpe:2.3:a:apache:zookeeper:3.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.0-1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.0-1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.1-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.1-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.1-1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.1-1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.2-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.2-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.3-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.3-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.4-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.4-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.5:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.5-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.5-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.8.6:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.8.6:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.0-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.0-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.0-1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.0-1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.1-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.1-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.2-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.2-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.3-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.3-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.3-1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.3-1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.3-2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.3-2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.4:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.4:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.4-0:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.4-0:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.4-1:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.4-1:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.4-2:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.4-2:*:*:*:*:*:*:*
  • cpe:2.3:a:apache:zookeeper:3.9.5:*:*:*:*:*:*:*
    cpe:2.3:a:apache:zookeeper:3.9.5:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-59739: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-97318 – The Giveaways and Contests by RafflePress WordPress plugin before 1.12.27 does not properly validate a giveaway's parent page URL before saving it...
  • CVE-2026-97317 – The Giveaways and Contests by RafflePress WordPress plugin before 1.12.27 does not remove the reCAPTCHA secret key from the giveaway settings it e...
  • CVE-2026-94298 – The BuildKit WordPress plugin before 1.0.29 does not properly sanitise and escape data submitted by contributor-level users before storing it and ...
  • CVE-2026-92820 – The Ninja Forms - File Uploads plugin for WordPress is vulnerable to arbitrary file operations in all versions up to, and including, 3.3.34 via the...
  • CVE-2026-92174 – The SiteOrigin Widgets Bundle plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.73.2 via the 'them...