Cross-tenant code execution via predictable bucket names
Published Feb 20, 2026 · Updated Feb 20, 2026
Predictable bucket naming in Google Vertex AI Experiments before 1.133.0 allows remote attackers to execute code across tenants. Vertex AI Experiments derives a Cloud Storage bucket name predictably and accepts a pre-created, attacker-controlled bucket for experiment data. Exploitation requires bucket pre-creation before a victim experiment uses that name, enabling model theft, artifact poisoning, and code execution in the victim tenant.
Summary
What happened
Predictable bucket naming in Google Vertex AI Experiments before 1.133.0 allows remote attackers to execute code across tenants. Vertex AI Experiments derives a Cloud Storage bucket name predictably and accepts a pre-created, attacker-controlled bucket for experiment data. Exploitation requires bucket pre-creation before a victim experiment uses that name, enabling model theft, artifact poisoning, and code execution in the victim tenant.
The record
- CVE
- CVE-2026-2473
- Published
- Feb 20, 2026
- Updated
- Feb 20, 2026
- Vendor
- Go standard library
- Product
- Vertex AI Experiments
- Classifications
- CWE-340, CAPEC-253
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2026CVE publishedPublication date reported by the CVE source.
- Feb 20, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.21.0 <1.133.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo