Root cause
Customer authentication did not enforce the boundary around internal support-wide information. The researcher contrasted denied resource-specific operations with an accessible aggregate operation. This supports an authorization gap; middleware behavior and the intended management use remain hypotheses, not confirmed implementation details.
Demonstrated impact
Observed disclosures linked customer names or phone numbers with cases and agents, including agent activity. Phishing and harassment were potential consequences. Millions of affected records were estimated; conversation contents and call manipulation were not demonstrated.
What to check for
- Treat aggregate views as separately privileged resources; successful authentication is not evidence of permission to observe other users.
- Reducing identifiable details limits the harm when a support-data boundary fails. The source does not document the deployed authorization repair.
Award and evidence
How the award was verified, and what the record does not establish
Single report award includes a USD 1,000 report-quality bonus; no settlement date is given.
- Researcher-published evidence does not independently establish settlement, total affected population, backend implementation or deployed repair.
- The prerequisite was an ordinary signed-in account; describing the exposure as unauthenticated would erase that requirement.
Timeline
- Published
- 2026-03-31explicit
- Public Disclosure
- 2026-03-31explicit
- Reported
- 2025-06-01explicit
- Awarded
- 2025-06-10explicit
Related cases
- Google Mamba temporary outputs lacked access isolation
Google · Authorization and tenant boundaries · USD 37,604.40
- Google Firefly confused worker authority and storage boundaries
Google · Authorization and tenant boundaries · USD 60,000
- Google Application Integration mixed resource and service authority
Google · Authorization and tenant boundaries · USD 75,000
- GitHub comparison output lacked source-repository authorization
GitHub · Authorization and tenant boundaries · USD 10,000
- Chrome graphics input validation weakened an isolation boundary
Google · Client and browser security · USD 250,000
- Google device grants lost client and permission binding
Google · Authentication and identity · USD 13,337
Sources
- Hacking Google Support: Leaking millions of customer records ($14k bounty)Michael Dalton · reviewed 2026-10-03
Record reviewed 2026-10-03. Snapshot af2809c308fc. Open the complete JSON contract.