Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-19486 – SSRF Leading to Cloud Credential Theft – Google Cloud Gemini Enterprise Agent Platf

Be the first to know when new zero-days emerge:

Summary

CVE-2026-19486 is a Server-Side Request Forgery (SSRF) vulnerability in Google Cloud’s Gemini Enterprise Agent Platform App Builder that allowed unauthenticated, remote attackers to leak the Compute Engine default service account access token. The flaw carries a CVSS v4.0 base score of 8.7 (High) and requires no privileges or user interaction to exploit, making it exploitable directly over the network against any exposed, vulnerable App Builder deployment.

Technical details

  • Root cause: The App Builder component failed to adequately restrict or validate server-side outbound requests, allowing an attacker to induce the application to make requests on its behalf (CWE-918, CAPEC-664: Server Side Request Forgery).
  • Trigger conditions: An attacker sends crafted input to a vulnerable App Builder deployment that causes the backend to issue a request to an internal metadata endpoint (consistent with the well-known Compute Engine instance metadata service used to obtain the default service account’s access token).
  • Attack vector: Network — the vulnerability is remotely exploitable, requires no authentication (PR:N) and no user interaction (UI:N), per the CVE record’s CVSS:4.0 vector.
  • Impact: Successful exploitation discloses the Compute Engine default service account access token, which could then be used to interact with Google Cloud APIs and resources with the privileges granted to that service account — potentially enabling further lateral movement, data access, or resource manipulation within the victim’s Google Cloud environment.

Affected software

  • Google Cloud Gemini Enterprise Agent Platform — App Builder
  • Confirmed affected for deployments created/active between October 11, 2025 and June 1, 2026 (per the official CVE record’s version-affected range)

Severity

  • CVSS v4.0 Base Score: 8.7 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:L/SI:L/SA:L/U:Amber

Mitigation and recommended actions

  • Immediate: Google patched the underlying platform issue on June 1, 2026. Because the vulnerability affected the App Builder’s generated/deployed application logic, organizations must redeploy any previously deployed App Builder applications to pick up the fix — patching the platform alone does not remediate apps deployed before the fix.
  • Verification: Confirm redeployment occurred after June 1, 2026, and review Google Cloud’s Gemini Enterprise Agent Platform release notes (July 20, 2026 entry) for the official fix announcement.
  • If immediate redeployment is not possible: Restrict network egress from App Builder-hosted applications to the Compute Engine metadata service (169.254.169.254) where feasible, and monitor for anomalous outbound requests originating from App Builder application instances to internal-only or link-local addresses.
  • General hardening: Apply the principle of least privilege to the Compute Engine default service account used by App Builder deployments to limit the blast radius should token leakage recur.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge