A SQL injection (CWE-89) and security boundary bypass (CWE-863) vulnerability exists in the prebuilt BigQuery forecasting tool (bigquery-forecast)… (CVE-2026-15829)
A SQL injection and security boundary bypass vulnerability exists in the prebuilt BigQuery forecasting tool (bigquery-forecast) of googleapis/mcp-toolbox. The tool improperly interpolates client-controlled parameters into SQL queries without proper escaping, allowing attackers to inject multi-statement or cross-dataset queries. This bypasses the intended allowedDatasets restrictions and permits unauthorized reading of arbitrary BigQuery tables. No patch information is provided, and no known exploits are reported in the wild. The vulnerability is rated high severity based on its impact.
AI Analysis
Technical Summary
The prebuilt BigQuery forecasting tool (bigquery-forecast) in googleapis/mcp-toolbox accepts client-controlled parameters (data_col, timestamp_col, and id_cols) as plain strings and directly interpolates them via fmt.Sprintf into AI.FORECAST table-valued SELECT statements without escaping. Although the tool uses an allowedDatasets mechanism to restrict queries, this mechanism only validates the history_data parameter and does not re-validate the final assembled query. Consequently, an attacker can break out of string literal fields to inject multi-statement or cross-dataset queries, bypassing dataset boundaries and accessing unauthorized BigQuery tables.
Potential Impact
An attacker with the ability to control certain query parameters can perform SQL injection to execute unauthorized queries across dataset boundaries. This leads to unauthorized disclosure of arbitrary BigQuery tables beyond the operator-configured allowedDatasets restrictions. The vulnerability compromises data confidentiality within the affected environment.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using the vulnerable parameters with untrusted input or apply strict input validation and escaping on client-controlled parameters to prevent injection. Monitor vendor channels for updates regarding patches or official mitigations.
A SQL injection (CWE-89) and security boundary bypass (CWE-863) vulnerability exists in the prebuilt BigQuery forecasting tool (bigquery-forecast)… (CVE-2026-15829)
Description
A SQL injection and security boundary bypass vulnerability exists in the prebuilt BigQuery forecasting tool (bigquery-forecast) of googleapis/mcp-toolbox. The tool improperly interpolates client-controlled parameters into SQL queries without proper escaping, allowing attackers to inject multi-statement or cross-dataset queries. This bypasses the intended allowedDatasets restrictions and permits unauthorized reading of arbitrary BigQuery tables. No patch information is provided, and no known exploits are reported in the wild. The vulnerability is rated high severity based on its impact.
CVSS v4.0
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The prebuilt BigQuery forecasting tool (bigquery-forecast) in googleapis/mcp-toolbox accepts client-controlled parameters (data_col, timestamp_col, and id_cols) as plain strings and directly interpolates them via fmt.Sprintf into AI.FORECAST table-valued SELECT statements without escaping. Although the tool uses an allowedDatasets mechanism to restrict queries, this mechanism only validates the history_data parameter and does not re-validate the final assembled query. Consequently, an attacker can break out of string literal fields to inject multi-statement or cross-dataset queries, bypassing dataset boundaries and accessing unauthorized BigQuery tables.
Potential Impact
An attacker with the ability to control certain query parameters can perform SQL injection to execute unauthorized queries across dataset boundaries. This leads to unauthorized disclosure of arbitrary BigQuery tables beyond the operator-configured allowedDatasets restrictions. The vulnerability compromises data confidentiality within the affected environment.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, avoid using the vulnerable parameters with untrusted input or apply strict input validation and escaping on client-controlled parameters to prevent injection. Monitor vendor channels for updates regarding patches or official mitigations.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-wvx3-gvxv-cmxc
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-15829"]
- Ecosystems
- []
- Database Specific Severity
- HIGH
- Cvss Version
- 4.0
Threat ID: 6a5fcf401010f89cc2151837
Added to database: 07/21/2026, 19:57:52 UTC
Last enriched: 07/21/2026, 20:35:34 UTC
Last updated: 07/21/2026, 21:43:14 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.