# CVE-2026-19485: Bucket Squatting in Vertex AI Search for Commerce

> Attackers can access staged data and logs via predictable bucket names in Vertex AI Search for Commerce.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/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:** 26 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-5mff-2rmc-p8x8

## What is CVE-2026-19485?

CVE-2026-19485 is a critical vulnerability in Google Cloud Vertex AI Search for Commerce, published on 26 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A Predictable Resource Name vulnerability in BigQuery Import Staging in Google Cloud Vertex AI Search for Commerce versions prior to 2026-04-27 on Google Cloud Platform allows an attacker knowing the victim's project number to obtain read/write access to staged data and error logs using predictable bucket names.

This vulnerability was patched and no customer action is needed.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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


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

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

## Is CVE-2026-19485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19485 is a critical vulnerability in Google Cloud Vertex AI Search for Commerce, published on 26 Aug 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-19485 in the wild and no public exploit code.

Affected product: Google Cloud Vertex AI Search for Commerce. 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-19485/ (Markdown: https://insights.sbomify.com/CVE-2026-19485/index.md)
```

## Sources

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

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