CVE-2026-59565
Raw vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-59565 is a high-severity Improper Handling of Values (CWE-229) vulnerability in Zscaler Client Connector (inferred from references). Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 39th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-64881
Vulnerability Data
A remotely exploitable buffer overflow bug can cause a local and kernel denial-of-service attack on affected versions of Zscaler Client Connector on Windows.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly enforces correct handling of parameter counts and defined values before processing occurs.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require proper input validation and parameter handling to prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure development lifecycle includes input validation and parameter handling requirements that reduce missing-value errors.
A.8.26 requires identifying and specifying requirements (incl. input validation, resilience against SQLi/buffer overflows, integrity checks) that can address improper value handling during development, but this is only a minority slice of CWE-229's broad class of value-count/undefined cases across all input and parameter sites.
A.8.27 mandates security-by-design principles (e.g. distrust input, least privilege, fail securely, data validation/sanitization) and design reviews that can stop improper value handling from reaching production in many cases, but leaves a bounded remainder (e.g. legacy code, outsourced development where principles are only contractually required, or incomplete application of the full set of principles).
Secure coding standards mandate proper handling of missing or undefined parameters, directly addressing this weakness.