AAK-MCP-CLOUDRUN-CVE-2026-85297-001: Cloud Run MCP below 1.11.0: source deploys use a bucket named after the project without checking who owns it
- Severity
- HIGH
- Category
- Supply Chain (
supply-chain) - Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py- Auto-fixable
- No.
- SARIF name
CloudRunMcpSourceBucketSquatting
What it detects
Cloud Run MCP (@google-cloud/cloud-run-mcp, GoogleCloudPlatform/cloud-run-mcp) deploys local source to Cloud Run by uploading an archive to a Cloud Storage bucket named <project id>-source-bucket and building from it. Before 1.11.0 it used an existing bucket of that name without checking which project owns it. Bucket names are global, so a bucket created first under that name in another project, and left open to writes, receives the source: its owner can read it, or change it before Cloud Build runs it (CVE-2026-85297, CVSS 4.0 7.7, CWE-340). 1.11.0 checks that the bucket belongs to the deploying project and otherwise uses a randomized name (GoogleCloudPlatform/cloud-run-mcp#300).
How to fix
Upgrade @google-cloud/cloud-run-mcp to 1.11.0 or later and pin it, in place of the unscoped cloud-run-mcp, whose only release is 1.0.0. If an earlier release has deployed source, check that <project id>-source-bucket belongs to your project, and redeploy from a known-good tree if it does not.
To confirm the finding is gone, report only this rule:
agent-audit-kit scan . --rules AAK-MCP-CLOUDRUN-CVE-2026-85297-001
Limitations
Reports an npm reference to @google-cloud/cloud-run-mcp below 1.11.0 that states a version: a package.json or lockfile entry, or the package in an MCP config, reporting a range that admits an affected version. latest was 1.11.0 on 2026-10-27 and states no version, so the README's own unversioned npx -y @google-cloud/cloud-run-mcp is not reported. The unscoped npm cloud-run-mcp is the same 1.0.0 build under the project's first name, and that is its only release, so any reference to it is reported, an unversioned one included; that takes in an MCP server run by the bare name cloud-run-mcp, which is also the executable a global install of the scoped package provides. It reads the version, not whether the server ever deploys from source, nor which bucket a past deploy used. Docker's MCP catalog image mcp/cloud-run-mcp is tagged only latest, the remote-server image us-docker.pkg.dev/cloudrun/container/mcp carries no version tag, and the Gemini CLI extension installs from the repository, so none states a version AAK reads and none is reported. 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-85297
- OWASP MCP Top 10: MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
- OWASP Agentic Top 10: ASI04 (Agentic Supply Chain Vulnerabilities), ASI05 (Unexpected Code Execution (RCE))
- Adversa AI MCP Top 25 (AAK-defined ids): ADV-EXFIL-02 (Source File Exfiltration)
- CSA AI Controls Matrix (AICM): AIS-07, 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-CLOUDRUN-CVE-2026-85297-001.md: the page then shows that text, with the registry reference appended under it.