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.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/googleapis/mcp-toolbox/pull/3341 Patch, Third Party Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 9.3 · googleNVD modified 2026-10-26 11:10
Affected (CPE criteria) 1
cpe:2.3:a:google:mcp_toolbox_for_databases:*:*:*:*:*:*:*:*
References 1
- https://github.com/googleapis/mcp-toolbox/pull/3341 Patch, Third Party Advisory