How severe is CVE-2026-2473?

No CVSS score has been assigned to CVE-2026-2473 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-2473?

CVE-2026-2473 affects the following packages: google-cloud-aiplatform (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-2473?

Update google-cloud-aiplatform to 1.133.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2473 is resolved across your whole dependency graph.

How do I detect CVE-2026-2473 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google-cloud-aiplatform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-2473 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2026-2473 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-2473 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-2473?

CVE-2026-2473 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-2473?

CVE-2026-2473 is classified as CWE-340 (CWE-340). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2026-2473 published, and has it been updated?

CVE-2026-2473 was published on February 20, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

Not in CISA KEV

CVE-2026-2473 — google-cloud-aiplatform

CVE-2026-2473 is a CWE-340 vulnerability in google-cloud-aiplatform. A fix is available for google-cloud-aiplatform — see the affected versions and patch details below.

Google Cloud Vertex AI has a a vulnerability involving predictable bucket naming

Also known asPYSEC-2026-2500

Published

Feb 20, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-2473.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐍google-cloud-aiplatform

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Predictable bucket naming in Vertex AI Experiments in Google Cloud Vertex AI from version 1.21.0 up to (but not including) 1.133.0 on Google Cloud Platform allows an unauthenticated remote attacker to achieve cross-tenant remote code execution, model theft, and poisoning via pre-creating predictably named Cloud Storage buckets (Bucket Squatting).

This vulnerability was patched and no customer action is needed.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`google-cloud-aiplatform`	≥ 1.21.0&&< 1.133.0	1.133.0`pip install --upgrade 'google-cloud-aiplatform==1.133.0'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for google-cloud-aiplatform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update google-cloud-aiplatform to 1.133.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2473 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.