AAK-MCP-TOOLBOX-CVE-2026-93328-001: Google MCP Toolbox 1.2.0 to 1.4.x: the Cloud Storage tools take any bucket and any local path
- Severity
- CRITICAL
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
McpToolboxCloudStorageUnrestricted
What it detects
Google MCP Toolbox for Databases (googleapis/mcp-toolbox), which MCP clients start through the npm launcher @toolbox-sdk/server, has a Cloud Storage source from 1.2.0 whose tools take the bucket and the local path from the tool call. Before 1.5.0 nothing limits either: upload_object sends any file the server process can read to whatever bucket the call names, download_object writes over any file it can write, and ValidateLocalPath asks only for an absolute path with no .. segment. Anyone who can invoke those tools can send host files to a bucket outside the project or overwrite local files (CVE-2026-93328, CVSS 4.0 9.3, CWE-22/CWE-862). 1.5.0 adds the allowedBuckets and allowedLocalRoots source options (googleapis/mcp-toolbox#3454), and both still allow everything when omitted.
How to fix
Upgrade @toolbox-sdk/server, and any toolbox binary or image, to 1.10.0 or later and pin it (1.5.0 adds the options; 1.10.0 also fixes CVE-2026-102242), then set allowedBuckets and allowedLocalRoots on every cloud-storage source: with either omitted, every bucket, or every absolute path the server process can reach, is allowed.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-TOOLBOX-CVE-2026-93328-001
Limitations
Reports an npm reference to @toolbox-sdk/server from 1.2.0 below 1.5.0 that states a version: a package.json or lockfile entry, or the launcher in an MCP config, reporting a range that admits an affected version. latest was 1.15.0 on 2026-10-27 and states no version, so an unversioned reference is not reported here (AAK-MCP-TOOLBOX-CVE-2026-102242-001 reports one as unpinned). It reads the version, not the toolbox configuration: a server with no cloud-storage source is reported too, and 1.5.0 and later are not reported although a cloud-storage source that sets neither option is as exposed. The launcher runs the binary of its own version, so its number is the server's; a toolbox binary started by path, or the container image, states no version AAK reads and is not reported. 1.2.0 to 1.4.x also fire AAK-MCP-TOOLBOX-CVE-2026-102242-001. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.
References
- CVE: CVE-2026-93328
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering), MCP07:2025 (Insufficient Authentication & Authorization)
- OWASP Agentic Top 10: ASI02 (Tool Misuse and Exploitation), ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-INJECT-06 (Tool Param Path Traversal), ADV-SCOPE-02 (Filesystem Root Access)
- CSA AI Controls Matrix (AICM): AIS-07, IAM-01, STA-08
All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-TOOLBOX-CVE-2026-93328-001.md: the page then shows that text, with the registry reference appended under it.