Skip to main content
VulnerabilityPublished Updated

CVE-2026-14541: An authentication bypass and audience confusion vulnerability exists in the Google OAuth provider component of Google mcp-toolbox version 1.4.0

Affects mcp-toolboxSource GCVE Database

0
Compare
Authoritative record:CVE-2026-14541· High 8.0

Not known to be exploited · CVSS 8.0 High.

Data as of 7 Nov 2026, 23:24 UTC

CVSS 4.0 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 7 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubgoogleapis/mcp-toolboxpkg:github/googleapis/mcp-toolboxOther threatsAffected
  • =1.4.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Until a fix is available, ensure that the Google authService is initialized with an explicitly defined audience or clientId to enforce proper audience validation and prevent acceptance of tokens intended for other applications.

Description

CVE-2026-14541 is a high severity authentication bypass and audience confusion vulnerability in the Google OAuth provider component of Google mcp-toolbox version 1.4.0. When initialized with mcpEnabled: true but without an explicitly defined audience or clientId, the token validation process skips audience checks. This allows acceptance of any valid Google OAuth access token, even those intended for unrelated applications, potentially granting unauthorized access to protected tools and data backends.

References

Community reviews

Loading reviews…