CVE-2026-14541 Google CVE debrief

Who should care

Users of Google mcp-toolbox version 1.4.0, administrators of protected tools and data backends, security teams responsible for monitoring and responding to potential security incidents, and operators of affected systems should be aware of this vulnerability and take necessary precautions to protect their systems and data. They should also review compensating controls for exposed systems while remediation is scheduled and verified, and track exceptions, retest remediated assets, and close the item only after evidence is documented. Additionally, they should confirm whether affected product deployments exist in managed environments and assign an owner for follow-up, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed. Furthermore, they should check relevant monitoring, detection, and logs for exposed assets that need extra review, and implement compensating controls for exposed systems while remediation is scheduled and verified. Finally, they should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and verify and explicitly define audience or clientId for Google authService, restrict access to protected tools and data backends, and monitor for suspicious activity, and implement compensating controls, and exception tracking and retest, and verify whether affected product deployments exist in managed environments and assign an owner for follow-up, and review compensating controls for exposed systems while remediation is scheduled and verified, and check relevant monitoring, detection, and logs for exposed assets that need extra review, and track exceptions, retest remediated assets, and close the item only after evidence is documented, and plan vendor-supported updates or mitigations through normal change control where exposure is confirmed, and review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance, and verify and explicitly define audience or clientId for Google authService, restrict access to protected tools and data backends, and monitor for suspicious activity, and implement compensating and

Technical summary

The 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. This allows the toolbox to accept any valid Google OAuth access token—even those minted for unrelated ecosystem applications—granting unauthorized clients access to protected tools and data backends. Users should verify and explicitly define audience or clientId for Google authService, restrict access to protected tools and data backends, and monitor for suspicious activity.

Defensive priority

High priority due to potential for unauthorized access to protected tools and data backends.

Recommended defensive actions

• Verify and explicitly define audience or clientId for Google authService
• Restrict access to protected tools and data backends
• Monitor for suspicious activity
• Implement compensating controls
• Exception tracking and retest

Evidence notes

Evidence is limited; further verification needed to determine affected scope and potential impact. The CVE record was published on 2026-07-31T03:16:24.170Z and has not been modified since then. The Google OAuth provider component of Google mcp-toolbox version 1.4.0 is vulnerable to authentication bypass and audience confusion. The ValidateMCPAuth pipeline for opaque tokens skips audience validation entirely when a Google authService is initialized with mcpEnabled: true but lacks an explicitly defined audience or clientId.

Official resources