Severity by source
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear
Network-reachable managed API with low-privilege GCP access and known project number (PR:L, AC:L); predictable bucket names break tenant isolation, yielding scope change (S:C) with high confidentiality and integrity but no availability impact.
Primary rating from Vendor (GoogleCloud).
CVSS VectorVendor: GoogleCloud
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Clear
Lifecycle Timeline
3DescriptionCVE.org
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.
AnalysisAI
Cross-tenant data exposure in Google Cloud Vertex AI Search for Commerce (versions prior to 2026-04-27) allowed an authenticated attacker who knew a victim's Google Cloud project number to read from and write to the Cloud Storage buckets used for BigQuery Import staging, because those bucket names were predictably derived rather than randomized. An attacker could reach another tenant's staged catalog data and import error logs, breaching data confidentiality and integrity across project boundaries. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the target used the BigQuery Import staging feature of Vertex AI Search for Commerce on a version prior to 2026-04-27, and that the attacker possesses the victim's Google Cloud project number, from which the predictable staging bucket name is derived to gain read/write access to staged data and error logs. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The vendor CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N, base 9.3) reflects a network-reachable, low-complexity issue requiring only low privileges and no user interaction, with high confidentiality and integrity impact on both the vulnerable and a subsequent (cross-tenant) system - appropriate for a broken-isolation bug. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | No customer action is required: Google applied the fix to the managed service as of 2026-04-27 (Vendor-released patch: service update dated 2026-04-27), which replaces the predictable staging bucket naming with unguessable identifiers, so tenants running the current service are already remediated. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, identify whether your organization uses Google Cloud Vertex AI Search for Commerce and document affected teams and projects. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-330 – Use of Insufficiently Random Values
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-66653
GHSA-5mff-2rmc-p8x8