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.
Project Subscriptions
No data.
Advisories
No advisories yet.
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
| Link | Providers |
|---|---|
| https://github.com/zscaler/zscaler-mcp-server/pull/41 |
|
History
Mon, 28 Sep 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | HMAC Confirmation Token Unbinding in zscaler-mcp-server | |
| Weaknesses | CWE-305 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: Zscaler
Published:
Updated: 2026-09-28T13:31:27.587Z
Reserved: 2026-07-06T06:18:59.633Z
Link: CVE-2026-59563
No data.
Status : Received
Published: 2026-09-28T13:17:22.160
Modified: 2026-09-28T13:17:22.160
Link: CVE-2026-59563
No data.
OpenCVE Enrichment
No data.
Weaknesses