How severe is CVE-2026-2472?

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

Which packages are affected by CVE-2026-2472?

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

How do I fix CVE-2026-2472?

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

How do I detect CVE-2026-2472 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-2472 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.

How does O3 Security protect against CVE-2026-2472?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-2472 can be triaged on real exposure rather than presence alone.

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

Yes. There are 1 known exploit references for CVE-2026-2472, including . All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2026-2472 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 45th 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-2472?

CVE-2026-2472 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2026-2472 was published on February 20, 2026 and was last updated on July 13, 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-2472 — google-cloud-aiplatform

Fix: googleapis/python-aiplatform@8a00d43

CVE-2026-2472 is a Cross-site Scripting (XSS) vulnerability in google-cloud-aiplatform. 1 public exploit reference exists, so weaponization risk is real. A fix is available for google-cloud-aiplatform — see the affected versions and patch details below.

Google Cloud Vertex AI SDK affected by Stored Cross-Site Scripting (XSS)

Also known asPYSEC-2026-2499

Published

Feb 20, 2026

Updated

Jul 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

Exploitation data as of Sep 23, 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-2472.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs45th percentile — riskier than 45% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Stored Cross-Site Scripting (XSS) in the _genai/_evals_visualization component of Google Cloud Vertex AI SDK (google-cloud-aiplatform) versions from 1.98.0 up to (but not including) 1.131.0 allows an unauthenticated remote attacker to execute arbitrary JavaScript in a victim's Jupyter or Colab environment via injecting script escape sequences into model evaluation results or dataset JSON data.

Affected Packages

1 total 1 fixed

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

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

JoshuaProvoste/CVE-2026-2472-Vertex-AI-SDK-Google-Cloud

Technical PoC for CVE-2026-2472 (GCP-2026-011): Unauthenticated and Stor

⭐ 5🍴 1Feb 2026

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.131.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-2472 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.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2026-2472 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2026-2472. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

Product	Fixed in	Advisory
Red Hat OpenShift AI 2.25	`rhoai/odh-llama-stack-core-rhel9:1775144403`	RHSA-2026:10184

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2026-2472 in your dependencies?

O3 Security finds CVE-2026-2472 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works