SSRF (Server-Side Request Forgery) in Google Cloud Gemini Enterprise Agent Platform App Builder (CVE-2026-19486)
Summary
SSRF in Google Cloud Gemini Enterprise Agent Platform App Builder (CVE-2026-19486). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
A Server-Side Request Forgery (SSRF) vulnerability in Google Cloud Gemini Enterprise Agent Platform App Builder versions prior to 2026-06-01 on Google Cloud Platform allows an unauthenticated attacker to leak the Compute Engine default service account access token.
This vulnerability was patched on 01 June 2026. Users will need to redeploy their previously deployed apps.
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-19486 has been found in Google Cloud Gemini Enterprise Agent Platform App Builder.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Google Cloud Gemini Enterprise Agent Platform App Builder CVE-2026-19486" on the vendor's site.
CVE-2026-19486 (Google Cloud Gemini Enterprise Agent Platform App Builder) — CWE-918
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.
SSRF (CWE-918) exists in Google Cloud Gemini Enterprise Agent Platform App Builder.
Check the vendor advisory for the affected versions of Google Cloud Gemini Enterprise Agent Platform App Builder.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Google Cloud Gemini Enterprise Agent Platform App Builder を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web docs.cloud.google.com
- web nvd.nist.gov
- web github.com