Github.Com Googleapis Mcp-Toolbox vulnerabilities
6 known vulnerabilities affecting github.com/googleapis_mcp-toolbox.
Total CVEs
6
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL5HIGH1
Vulnerabilities
Page 1 of 1
CVE-2026-11717P3CRITICAL≥ 0, < 1.4.02026-06-18
CVE-2026-11717 [CRITICAL] CWE-287 googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken)
googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken)
An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.
When verifying an unparsed opaque token via an OAuth 2.0 introspection en
ghsa
CVE-2026-11720P3CRITICAL≥ 0, < 1.3.02026-06-29
CVE-2026-11720 [CRITICAL] CWE-22 MCP Toolbox HTTP tool path parameters allow traversal to unintended endpoints
MCP Toolbox HTTP tool path parameters allow traversal to unintended endpoints
A path traversal vulnerability exists in the HTTP tool URL builder of googleapis/mcp-toolbox.
When constructing downstream API requests, the URL builder substitutes user-controlled pathParams into the configured tool path and parses the resulting string as a relative URL. While it checks that the input does
ghsa
CVE-2026-11718P3CRITICAL≥ 0, < 1.4.02026-06-18
CVE-2026-11718 [CRITICAL] CWE-287 googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken)
googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken)
An authentication bypass vulnerability exists in the generic opaque token validation path (validateOpaqueToken) of googleapis/mcp-toolbox.
When the toolbox validates an opaque token via an OAuth 2.0 introspection
ghsa
CVE-2026-11719P3HIGH≥ 0, < 1.4.02026-06-18
CVE-2026-11719 [HIGH] CWE-862 MCP Toolbox for Databases: authenticated authorization bypass
MCP Toolbox for Databases: authenticated authorization bypass
An authenticated authorization bypass vulnerability exists in MCP Toolbox for Databases due to missing scope enforcement across older protocol handlers.
While the 2025-11-25 protocol version handler correctly enforces per-tool restrictions defined by scopesRequired, older supported protocol versions (2025-06-18, 2025-03-26, and 2024-11-05) om
ghsa
CVE-2026-9739P3CRITICAL≥ 0, < 1.2.02026-05-28
CVE-2026-9739 [CRITICAL] CWE-942 MCP Toolbox for Databases vulnerable to DNS rebinding attacks
MCP Toolbox for Databases vulnerable to DNS rebinding attacks
Vulnerable to DNS rebinding attacks when using SSE (http://b/499408790). During the beta phase, we implemented `allowed-origins` and `allowed-hosts` flags to align with MCP security guidelines. However, the hardcoded `Access-Control-Allow-Origin: *` header in the SSE initialization handler was inadvertently retained. This vulnerability spec
ghsa
CVE-2026-11624P3CRITICAL≥ 0, < 0.25.02026-06-13
CVE-2026-11624 [CRITICAL] CWE-346 MCP Toolbox for Databases has an Origin Validation Error
MCP Toolbox for Databases has an Origin Validation Error
The Model Context Protocol has a security warning advising servers to validate the "Origin" header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin's host. In v0.25.0, a new "--allowed-hosts" flag was introduced alongside the existing "--allowed-origins" flag, enablin
ghsa