Control bypass through improper input validation
Published Sep 14, 2026 · Updated Sep 14, 2026
Improper input validation in Zscaler Client Connector before 4.2.0.152 allows attackers to bypass controls on Android and ChromeOS. Zscaler has not disclosed the affected input, code locus, or validation operation, so the exact mechanism is not public. The available record does not identify an authentication, interaction, or access prerequisite; the reported consequence is limited to bypass of Zscaler-enforced controls.
Summary
What happened
Improper input validation in Zscaler Client Connector before 4.2.0.152 allows attackers to bypass controls on Android and ChromeOS. Zscaler has not disclosed the affected input, code locus, or validation operation, so the exact mechanism is not public. The available record does not identify an authentication, interaction, or access prerequisite; the reported consequence is limited to bypass of Zscaler-enforced controls.
The record
- CVE
- CVE-2026-59569
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Zscaler
- Product
- Zscaler Client Connector
- Classifications
- T1629, T1687
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <Android: 4.2.0.152
- Affected versionversion=0 <ChromeOS: 4.2.0.152
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo