# CVE-2026-59566: Local denial-of-service

> A local buffer overflow in Zscaler Client Connector allows attackers to cause a denial-of-service on Android and ChromeOS devices.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-j5x2-m45x-3cp3

## What is CVE-2026-59566?

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

### Official description

A locally exploitable buffer overflow bug can cause a local denial-of-service attack on affected versions of Zscaler Client Connector on Android and ChromeOS.

Weakness: CWE-229 (Improper Handling of Values)

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


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

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

## Is CVE-2026-59566 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59566 is a high-severity denial of service vulnerability in Zscaler Client Connector, published on 24 Aug 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-59566 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-59566/ (Markdown: https://insights.sbomify.com/CVE-2026-59566/index.md)
```

## Sources

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

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