# CVE-2026-15829: SQL Injection and Security Boundary Bypass in googleapis/mcp-toolbox

> Attackers can inject SQL into BigQuery forecasting tools to bypass dataset restrictions and read arbitrary tables.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jul 2026
- **Updated:** 22 Jul 2026
- **Also known as:** GHSA-wvx3-gvxv-cmxc

## What is CVE-2026-15829?

CVE-2026-15829 is a high-severity SQL injection vulnerability in MCP Toolbox for Databases (googleapis/mcp-toolbox), published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A SQL injection (CWE-89) and security boundary bypass (CWE-863) vulnerability exists in the prebuilt BigQuery forecasting tool (bigquery-forecast) of googleapis/mcp-toolbox.

The tool accepts client-controlled parameters (data_col, timestamp_col, and id_cols) as plain strings and interpolates them unescaped via fmt.Sprintf directly into a generated AI.FORECAST table-valued SELECT statement. While MCP Toolbox utilizes an allowedDatasets mechanism to restrict queries, this defense only validates the history_data parameter; the final assembled query is executed without re-validation.

An attacker can break out of the string literal fields (such as timestamp_col) to inject a valid multi-statement or cross-dataset query block. This allows an unauthorized user to bypass the operator-configured allowedDatasets boundary and read arbitrary BigQuery tables.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Google Mcp Toolbox for Databases.

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

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

## Is CVE-2026-15829 being exploited?

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

## Other vulnerabilities in MCP Toolbox for Databases (googleapis/mcp-toolbox)

- [CVE-2026-11720](https://insights.sbomify.com/CVE-2026-11720/): Path Traversal in googleapis/mcp-toolbox HTTP Tool URL Builder (critical 9.3)
- [CVE-2026-11717](https://insights.sbomify.com/CVE-2026-11717/): googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken) (critical 9.3)
- [CVE-2026-11718](https://insights.sbomify.com/CVE-2026-11718/): googleapis/mcp-toolbox: authentication bypass vulnerability in the generic opaque token validation path (validateOpaqueToken) (critical 9.3)
- [CVE-2026-11719](https://insights.sbomify.com/CVE-2026-11719/): MCP Toolbox for Databases: authenticated authorization bypass (high 8.6)
- [CVE-2026-14537](https://insights.sbomify.com/CVE-2026-14537/): Authorization Bypass in MCP Toolbox Legacy HTTP Endpoints (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-15829 is a high-severity SQL injection vulnerability in MCP Toolbox for Databases (googleapis/mcp-toolbox), published on 21 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15829 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-15829/ (Markdown: https://insights.sbomify.com/CVE-2026-15829/index.md)
```

## Sources

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

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