Predictable bucket naming in Google Cloud Vertex AI Experiments
CVE-2026-2473 is a bucket-squatting vulnerability in Google Cloud Vertex AI Experiments affecting Google Cloud Vertex AI from version 1.21.0 up to, but not including, 1.133.0. The issue arises from predictable Cloud Storage bucket naming used by the service or associated workflow, allowing an attacker to pre-create the expected bucket name in their own Google Cloud project before the legitimate tenant does. Because the bucket name is globally unique and predictably derived, the attacker can cause Vertex AI Experiment-related operations to interact with attacker-controlled storage. According to the provided content, successful exploitation can lead to cross-tenant remote code execution, model theft, and model poisoning.
Are you exposed to this one?
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.