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)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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.6%, placing it in the 49th 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 or proof-of-concept reference is indexed, 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 Nov 8, 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.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs49th percentile — riskier than 49% 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

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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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

Workaround published by Red Hat

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Source: Red Hat security advisory for CVE-2026-2472 (CC BY 4.0)