CVE-2026-59563: zscaler-mcp-server · Authentication Bypass by Primary Weakness
Affects zscaler-mcp-serverSource CVE Database V5
Not known to be exploited · CVSS 4.6 Medium : upgrade to 0.7.2 when convenient.
Data as of 12 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.7.2
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 28 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.
What to do
Upgrade zscaler-mcp-server to 0.7.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Zscalerzscaler-mcp-server | Affected
| Fixed in
|
GitHubzscaler-mcp-serverpkg:github/zscaler-mcp-serverOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Zscaler MCP Server to version 0.7.2 or later, where the issue is fixed by binding HMAC confirmation tokens to their specific resource identifiers. No other mitigation is indicated.
Description
Zscaler MCP Server versions 0.7.0 and 0.7.1 has an issue where HMAC confirmation tokens were not bound to the target resource identifier, allowing an MCP client or agent to replay a token generated for one resource to affect another resource of the same type. This issue is fixed in version 0.7.2.