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

Google · Business logic and concurrency

Cloud Build approval was not bound to immutable code

Cloud Build could execute a different revision from the one a reviewer had approved. The researcher demonstrated execution of newer, unreviewed code; access to secrets or cloud resources depended on the build's permissions. A Google notice published by the researcher records a $30,000 award, with USD inferred from program context.

Read the original writeupUSD 30,000 reported award · Reviewed 2026-10-05

Root cause

Approval referred to contribution state that could still change, rather than the exact version reviewed. The researcher compared the version identifiable at approval with the revision the build later selected. The build assumed those versions still matched instead of preserving that link.

Demonstrated impact

The controlled demonstration executed a newer, unreviewed revision. Access to secrets or cloud resources was a potential consequence of the build’s assigned privileges, not evidence that all pipelines exposed those assets.

What to check for

  • Bind approval and execution to immutable content identities, with explicit confirmation when the intended revision is ambiguous.
  • The researcher’s fix analysis describes check-to-commit binding and explicit commit selection; it does not establish a universal patch recipe.
  • Limit build identity privileges and secret availability independently of human approval.

Award and evidence

USD 30,000Bug Bounty · Researcher Reported With Vendor Quote
How the award was verified, and what the record does not establish

The researcher-published Google notice states $30000.00 without an explicit currency code. USD is inferred from Google’s March 2017 program-wide USD statement, almost eight years before the January 2025 award, with October 2024 official context linking Cloud rewards to the broader Google VRP. This is denomination context, not independent proof of the individual award’s currency or cash settlement. Older reference; original report was in 2024.

  • The award notice is vendor correspondence reproduced by the researcher, not independently retrieved vendor evidence or proof of cash settlement.
  • The June 18, 2025 status change confirms the issue was marked fixed, not the exact deployment date.
  • The public account’s broader security consequences depend on pipeline permissions; no universal secret exposure is established.
  • The notice uses $ without spelling out USD. Currency is inferred from March 2017 Google VRP context, almost eight years before the award, and October 2024 Cloud-program continuity, about three months before it; neither independently proves this individual award’s denomination or settlement.

Timeline

Published
2025-07-21explicit
Public Disclosure
2025-07-21explicit · Publication of this write-up; earliest disclosure elsewhere was not independently established.
Reported
2024-11-13explicit
Awarded
2025-01-28explicit

Related visual models

Related cases

All 1 cases in Business logic and concurrency

Sources

  1. Who's SHA is it Anyway: Bypassing Google Cloud Build Comment Control for $30,000Adnan Khan · reviewed 2026-10-02
  2. Researcher-published Google award notice for the Cloud Build reportAdnan Khan, reproducing a Google award notice · reviewed 2026-10-05
  3. VRP news from NullconJosh Armour / Google · reviewed 2026-10-05
  4. Introducing Google Cloud’s new Vulnerability Reward ProgramMichael Cote and Sri Tulasiram / Google Cloud · reviewed 2026-10-05

Record reviewed 2026-10-05. 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