Vulnerability in Google Cloud Vertex AI Search for Commerce (CVE-2026-19485)
Summary
Vulnerability in Google Cloud Vertex AI Search for Commerce (CVE-2026-19485). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-19485 has been found in Google Cloud Vertex AI Search for Commerce.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Google Cloud Vertex AI Search for Commerce CVE-2026-19485" on the vendor's site.
CVE-2026-19485 (Google Cloud Vertex AI Search for Commerce) — CWE-330
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-330) exists in Google Cloud Vertex AI Search for Commerce.
Check the vendor advisory for the affected versions of Google Cloud Vertex AI Search for Commerce.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Google Cloud Vertex AI Search for Commerce を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web unit42.paloaltonetworks.com
- web nvd.nist.gov
- web unit42.paloaltonetworks.com
- web github.com