HMAC Confirmation Token Unbinding in zscaler-mcp-server
Priority LOW 20CWE-305Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- None · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00131 2nd percentileScored 2026-11-07
Fix Fixed zscaler-mcp-server (Zscaler): 0.7.2
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA zscaler-mcp-server (Zscaler) Fixed in 0.7.2
Timeline
- 2026-10-02 Threatist record created from CVE-2026-59563
- 2026-10-03 Alias added: GHSA-6wjq-5f4c-p8f7
References
More Zscaler vulnerabilities
- TI-2023-22133 Inappropriate file type control in Zscaler Proxy versions 3.6.1.25 and prior allows local… CVSS 3.1MEDIUM 5.5
- TI-2026-42530 Remote code execution in Zscaler Client Connector CVSS 3.1CRITICAL 9.1
- TI-2026-42526 Authentication bypass between ZCC and client connector portal CVSS 3.1CRITICAL 9.1
- TI-2020-09334 The Zscaler Client Connector for Windows prior to 2.1.2.74 had a stack based buffer… CVSS 3.1CRITICAL 9.8
- TI-2024-15528 Local Privilege Escalation via lack of input validation CVSS 3.1CRITICAL 9.8
- TI-2025-34691 SAML 2.0 Public Key Validation Issue CVSS 3.1CRITICAL 9.6
Sources
- CVE-2026-59563 · CVE Program
- CVE-2026-59563 · NVD
- FIRST EPSS
- GHSA-6wjq-5f4c-p8f7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences