CVE-2026-11717: Critical severity github/googleapis/mcp-toolbox vulnerability
An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.
When verifying an unparsed opaque token via an OAuth 2.0 introspection endpoint (RFC 7662), the toolbox decodes the response into an introspectResp struct where the Active field is declared as a pointer to a boolean (bool). The code only explicitly rejects a token if the response contains a populated active field set to false (if introspectResp.Active != nil && !introspectResp.Active). If an introspection endpoint responds with a payload that completely omits the mandatory active key, the internal variable remains nil, causing the conditional check to short-circuit. As a result, Toolbox accepts authorization tokens missing the "active" field, granting access to protected tools and underlying data sources.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/googleapis/mcp-toolboxto a version that resolves this vulnerability.Fixed in 1.4.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-11717?
The severity of CVE-2026-11717 is critical with a CVSS score of 9.3.
How do I fix CVE-2026-11717?
To fix CVE-2026-11717, update to the latest version of googleapis/mcp-toolbox that addresses this vulnerability.
What systems are affected by CVE-2026-11717?
CVE-2026-11717 affects the googleapis/mcp-toolbox library, specifically when utilizing the OAuth 2.0 introspection endpoint.
What type of vulnerability is CVE-2026-11717?
CVE-2026-11717 is classified as an authentication bypass vulnerability.
When was CVE-2026-11717 disclosed?
CVE-2026-11717 was disclosed on June 18, 2026.