An authentication bypass and audience confusion vulnerability exists in the Google OAuth provider component of Google mcp-toolbox version 1.4.0. When a Google authService is initialized with mcpEnabled: true but lacks an explicitly defined audience or clientId, the ValidateMCPAuth pipeline for opaque tokens skips audience validation entirely. As a result, the toolbox will accept any valid Google OAuth access token—even those minted for unrelated ecosystem applications—granting unauthorized clients access to protected tools and data backends.
Fix
Patch, vendor advisory and mitigation references on NVD 1
- https://github.com/googleapis/mcp-toolbox/pull/3450 Issue Tracking, Patch
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.0 · googleNVD modified 2026-10-23 23:10
Affected (CPE criteria) 1
cpe:2.3:a:google:mcp_toolbox_for_databases:1.4.0:*:*:*:*:*:*:*
References 1
- https://github.com/googleapis/mcp-toolbox/pull/3450 Issue Tracking, Patch