# CVE-2026-59570: Android ZCC denial of service

> A pre-installed peer app can disrupt the Zscaler tunnel, force logout, and toggle packet capture, causing denial of service and security bypass.

- **Severity:** High 7.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-cj79-f7p8-r2fv

## What is CVE-2026-59570?

CVE-2026-59570 is a high-severity denial of service vulnerability in Zscaler Client Connector, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On affected versions of Zscaler client connector, a pre-installed peer app can tear down the Zscaler tunnel, force user logout, and toggle packet capture.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-59570?


## How do I fix CVE-2026-59570?

No fix has been published for CVE-2026-59570 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-59570 being exploited?

There is no known exploitation of CVE-2026-59570 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-59570 and fix it if it is affected.

What it is: CVE-2026-59570 is a high-severity denial of service vulnerability in Zscaler Client Connector, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59570 in the wild and no public exploit code.

Affected product: Zscaler Client Connector. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-59570/ (Markdown: https://insights.sbomify.com/CVE-2026-59570/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-59570
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-59570
- OSV: https://osv.dev/vulnerability/CVE-2026-59570

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-59570/
Summaries are generated and may contain mistakes; the official description above is the record.