vulns.co
/
GKData.io MCP and API Buy me a coffee

Google · Authorization and tenant boundaries

Google Application Integration mixed resource and service authority

Google Application Integration did not consistently check resource ownership and the authority of backend tasks. The researcher reports cross-project access and test execution, but did not demonstrate completed code execution in production. He reports a $75,000 base award for this distinct finding.

Read the original writeupUSD 75,000 reported award · Reviewed 2026-10-03

Root cause

The service did not consistently check who owned a resource or what a backend task was allowed to do. The researcher compared customer-project permissions with backend integration-service permissions and found gaps between allowed customer actions and privileged service operations.

Demonstrated impact

The researcher reports cross-project access and test execution during authenticated testing. Production compromise potential was reportedly confirmed by Google, which stopped further testing; completed code execution in production was not demonstrated. Wider impact remains unverified.

What to check for

  • Authorize the actual resource owner at every service boundary rather than relying on an enclosing project context.
  • Independently constrain service-task authority even when the initiating user may legitimately configure an integration.
  • Use cross-tenant negative tests and track observed effects separately from vendor-assessed potential.

Award and evidence

USD 75,000Bug Bounty · Researcher Reported
How the award was verified, and what the record does not establish

Only the second report’s base award; excludes the later $13,337 and first report. USD remains contextual: Google’s July 2024 USD-denominated VRP announcement and October 2024 Cloud-program continuity statement, not settlement evidence.

  • Award and vendor impact assessment are researcher-published claims, not independently reviewed vendor correspondence.
  • The article-level CVE is not assigned here because its scope across the separate reports is ambiguous.
  • No precise fix date, payment occurrence or settlement date is established.
  • Currency inference uses 2024 program context, about two years before the award. The current Cloud policy uses a dollar symbol without an explicit USD statement; no independent settlement evidence is claimed.

Timeline

Published
2026-05-22explicit · Visible article header supplies May 22, 2026 and author Arvin Shivram.
Reported
2026-03-21explicit
Awarded
2026-04-28explicit

Related cases

All 19 cases in Authorization and tenant boundaries

Sources

  1. StubZero: $148,337 RCE in Google Cloud ProductionArvin Shivram (Brutecat) · reviewed 2026-10-03
  2. Increasing Google & Alphabet VRP rewards up to $151,515Sam Erb and Krzysztof Kotowicz / Google · reviewed 2026-10-03
  3. Introducing Google Cloud’s new Vulnerability Reward ProgramMichael Cote and Sri Tulasiram / Google Cloud · reviewed 2026-10-03

Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.

Library synced 2026-11-18 · cases last reviewed 2026-10-05

af2809c308fc · JSON exports & schemas · CC BY 4.0 content / MIT software