Skip to content
major vulnerability· requires attention

Zscaler Client Connector is widely deployed by enterprises; a bypass of its controls can undermine org-wide network security and is notable to all IT teams.

Applications

CVE-2026-59569

8.1
High
EPSS 0.12%Patch availableSep 15, 2026

Input-validation flaw in Zscaler Client Connector enabling security-control bypass.

common questions

Is CVE-2026-59569 being exploited?

Not confirmed. CVE-2026-59569 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.

How severe is CVE-2026-59569?

CVE-2026-59569 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-59569?

Yes. A fix has been recorded for CVE-2026-59569. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-59569 affect?

CVE-2026-59569 affects Zscaler Client Connector (Android), Zscaler Client Connector (ChromeOS). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-59569?

Apply vendor update ASAP; restrict unmanaged endpoints and monitor network traffic.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Zscaler Client Connector (Android)Zscaler Client Connector (ChromeOS)
impact

Allows attackers to bypass Zscaler traffic inspection/policy enforcement on Android/ChromeOS, enabling access to malicious sites and possible data exfiltration.

action required

Patch when possible

affected versions
Zscaler Client Connector
  • affected< Android: 4.2.0.152
  • affected< ChromeOS: 4.2.0.152

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free