CVE-2026-3259: Google Cloud BigQuery · Generation of error message containing sensitive information
Affects Google Cloud BigQuerySource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 01/29/2026 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 13% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 01/29/2026
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/U:ClearExploitation evidence
Disclosed: evidence found.
CVE published 23 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade Google Cloud BigQuery to 01/29/2026.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google CloudBigQuery | Affected
| Fixed in
|
AI-suggested
Google has patched this vulnerability as of January 29, 2026. Since BigQuery is a cloud-hosted service, Google manages the remediation and patch deployment. Customers do not need to take any action.
Description
A Generation of Error Message Containing Sensitive Information vulnerability in the Materialized View Refresh mechanism in Google BigQuery on Google Cloud Platform allows an authenticated user to potentially disclose sensitive data using a crafted materialized view that triggers a runtime error during the refresh process. This vulnerability was patched on 29 January 2026, and no customer action is needed.