A technical analysis by Tenable said nine cross-tenant vulnerabilities in Google Looker Studio disclosed in June 2025 could have allowed attackers to run arbitrary SQL queries and exfiltrate data across Google Cloud projects.
KEY FACTS
- Incident Nine cross-tenant vulnerabilities in Looker Studio
- Impact Could allow arbitrary SQL execution and data exfiltration
- Timeline Disclosed in June 2025 then patched by Google
- Exploitation No evidence of active exploitation in the wild
The flaws were given the collective name LeakyLooker and cover multiple attack paths including zero-click SQL injection on connectors and stored credentials, SQL injection through native functions, and leaks via hyperlinks and image rendering.
Successful abuse could let an attacker scan public reports or obtain access to private reports that use connectors such as BigQuery, then run queries across the owner’s entire Google Cloud project, potentially accessing or altering datasets.
One attack scenario involves a logic flaw in the copy report feature that can clone a report while retaining an owner’s credentials for JDBC connected sources, enabling deletion or modification of tables.
Another described path uses a specially crafted shared report that causes a viewer’s browser to contact an attacker controlled project, allowing one-click reconstruction or exfiltration of data from logs reported by the viewer.
WHY IT MATTERS
The flaws undermined the assumption that a report viewer cannot control the data they view, raising cross-tenant risks for organizations using Looker Studio connectors and cloud data services.