The vulnerability exists in the validateOpaqueToken function of googleapis/mcp-toolbox version 1.0.0. When validating opaque tokens via an OAuth 2.0 introspection endpoint, the response is decoded into an introspectResp struct. The subsequent validateClaims logic checks the issuer field with a condition that only executes if both the configured issuer and the token's issuer are non-empty strings. If the introspection response omits the issuer field, the token's issuer defaults to an empty string, causing the issuer verification block to be skipped. This flaw enables an attacker to bypass authentication by presenting tokens issued by unauthorized or unintended third-party identity providers.

Successful exploitation allows attackers to bypass authentication controls, potentially gaining unauthorized access to the MCP Toolbox for Databases. This can lead to unauthorized database operations or access to sensitive data managed by the toolbox. The vulnerability has a CVSS 4.0 score of 9.3 (critical), indicating high impact with network attack vector, no required privileges or user interaction, and high impact on confidentiality and integrity.

No official patch or remediation is currently available for this vulnerability. Users should monitor the vendor's advisory channels for updates. Until a fix is released, avoid using version 1.0.0 in production environments or implement additional external token validation controls to verify the issuer field explicitly. Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.