# CVE-2026-3259: Sensitive Data Disclosure in BigQuery via Materialized View Error Messages

> An authenticated user can disclose sensitive data via crafted materialized view error messages in Google BigQuery.

- **Severity:** High 7.1 (`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:Clear`)
- **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:** 23 Apr 2026
- **Updated:** 30 Apr 2026
- **Also known as:** GHSA-g3wg-j2ff-prcp

## What is CVE-2026-3259?

CVE-2026-3259 is a high-severity vulnerability in Google Cloud BigQuery, published on 23 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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


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

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

## Is CVE-2026-3259 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3259 is a high-severity vulnerability in Google Cloud BigQuery, published on 23 Apr 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-3259 in the wild and no public exploit code.

Affected product: Google Cloud BigQuery. 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-3259/ (Markdown: https://insights.sbomify.com/CVE-2026-3259/index.md)
```

## Sources

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

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