Skip to content
major vulnerability· requires attention

Affects Google Cloud service; allows authenticated users to execute privileged internal RPCs — high-impact cloud privilege escalation likely to be widely reported.

Cloud

CVE-2026-19759

9.4
Critical
EPSS n/aPatch availableSep 28, 2026

Authz flaw in Google Cloud Application Integration allows privileged internal RPC execution

common questions

Is CVE-2026-19759 being exploited?

Not confirmed. CVE-2026-19759 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-19759?

CVE-2026-19759 is rated Critical with a CVSS score of 9.4. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-19759?

Yes. A fix has been recorded for CVE-2026-19759. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-19759 affect?

CVE-2026-19759 affects Google Cloud Application Integration (< 2026-06-17), Google Cloud Platform (GCP). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-19759?

Confirm services are updated to 2026-06-17 patch and audit authenticated activity.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Google Cloud Application Integration (< 2026-06-17)Google Cloud Platform (GCP)
impact

Authenticated GCP user can invoke internal RPCs as a privileged identity, enabling privilege escalation and lateral access inside Google's production network.

action required

Monitor only

affected versions
Google Cloud Application Integration
  • affected< 2026-06-17

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free