# CVE-2026-93328: Missing Authorization in MCP Toolbox for Databases allows Arbitrary File Read and Write


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/U:Amber`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-2gc9-c85v-5vwr

## What is CVE-2026-93328?

CVE-2026-93328 is a critical vulnerability in MCP Toolbox for Databases (googleapis/mcp-toolbox), published on 26 Oct 2026. 

### Official description

Path Traversal and Missing Authorization in cloud-storage source in Google Cloud MCP Toolbox for Databases (googleapis/mcp-toolbox) versions 1.2.0 through 1.4.0 allows an unauthenticated remote attacker to exfiltrate host files to external Google Cloud Storage buckets and overwrite arbitrary local files via crafted tool invocation parameters.

Weakness: CWE-862 (Missing Authorization), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-93328?


## How do I fix CVE-2026-93328?

No fix has been published for CVE-2026-93328 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93328 being exploited?

There is no known exploitation of CVE-2026-93328 in the wild and no public exploit code.

Public exploit code:

- The authorization layer CVE-2026-93328 was missing: scoped grants, path confinement, and signed receipts in front of MCP storage tools. CVE reproduction + gated proof, 10/10 tests. (github_poc): https://github.com/sustilliano/cve-2026-93328-gate

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93328 and fix it if it is affected.

What it is: CVE-2026-93328 is a critical vulnerability in MCP Toolbox for Databases (googleapis/mcp-toolbox), published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-93328 in the wild and no public exploit code.

Affected product: MCP Toolbox for Databases (googleapis/mcp-toolbox). No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93328/ (Markdown: https://insights.sbomify.com/CVE-2026-93328/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93328
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93328
- OSV: https://osv.dev/vulnerability/CVE-2026-93328

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93328/
Summaries are generated and may contain mistakes; the official description above is the record.