Answer in brief
CVE-2026-11720 records a Critical severity (CVSS 9.3) vulnerability in Path Traversal in googleapis/mcp-toolbox HTTP Tool URL Builder. The current sources do not mark it as known exploited. The current feed maps Google/MCP Toolbox for Databases (googleapis/mcp-toolbox) (generic), github.com/googleapis/mcp-toolbox (go), github.com/googleapis/mcp-toolbox (go). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Google/MCP Toolbox for Databases (googleapis/mcp-toolbox) (generic), github.com/googleapis/mcp-toolbox (go), github.com/googleapis/mcp-toolbox (go). Check affected ranges and fixed versions before updating.
| Product | Affected versions | Fixed versions |
|---|---|---|
| cpe:2.3:a:google:mcp_toolbox_for_databases:*:*:*:*:*:*:*:* | Not reported | Not reported |
| Package | Affected range | Fixed version |
|---|---|---|
| Google/MCP Toolbox for Databases (googleapis/mcp-toolbox)generic | >=0 <1.3.0 | 1.3.0 |
| github.com/googleapis/mcp-toolboxgo | <1.3.0 | 1.3.0 |
| github.com/googleapis/mcp-toolboxgo | >=0 <1.3.0 | 1.3.0 |
Published upstream
Jun 29, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 29, 2026
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 not alter the scheme, host, or user info, it relies on ResolveReference for the final URL resolution. Because dot segments (../) are normalized during this resolution step, an attacker can supply path parameters containing directory traversal sequences to escape the operator-configured path scope. This allows the client to coerce the toolbox into making requests to unintended endpoints on the same target host while forwarding the toolbox's configured credentials (e.g., bypassing a restricted path like /api/v1/users/{{.id}} to reach /admin/secrets).
Quoted source text, attributed separately from HOL analysis.