Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-2472 high CVSS 8.1

Cross-Site Scripting (XSS) in google-cloud-aiplatform (CVE-2026-2472)

Summary

Cross-site scripting in google-cloud-aiplatform (CVE-2026-2472). Confidential information can be exposed externally. Mitigation: upgrade to 1.131.0 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-2472 has been found in google-cloud-aiplatform.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade google-cloud-aiplatform to 1.131.0 or later.
If unsure, ask your IT team or search "google-cloud-aiplatform CVE-2026-2472" on the vendor's site.

CVE-2026-2472 (google-cloud-aiplatform) — CWE-79 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated
Patched: 1.131.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in google-cloud-aiplatform.

📍 Affected scope

Check the vendor advisory for the affected versions of google-cloud-aiplatform.

🔥 Severity

Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 1.131.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'google-cloud-aiplatform' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'google-cloud-aiplatform' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で google-cloud-aiplatform を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade google-cloud-aiplatform to 1.131.0

    ステージング環境で 1.131.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

PyPI google-cloud-aiplatform
[{"type":"ECOSYSTEM","events":[{"introduced":"1.98.0"},{"fixed":"1.131.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details