Loading story…
Security researchers at Tenable disclosed nine cross-tenant vulnerabilities in Google Looker Studio (formerly Data Studio), collectively dubbed LeakyLooker, that could have allowed attackers to access other tenants’ data sources and run arbitrary SQL queries against victims’ connected databases. Reported impacts included potential data exfiltration as well as the ability to insert or delete data in connected services, with attack paths described as zero-click and one-click depending on the vector. Affected connectors and services potentially included Google Sheets, BigQuery, Spanner, Cloud Storage, and third-party databases such as PostgreSQL and MySQL, reflecting Looker Studio’s broad integration surface within Google Cloud environments.
The reported issues spanned multiple classes of cross-tenant weaknesses, including unauthorized access, SQL injection via database connectors and stored credentials, BigQuery/Spanner query abuse (including via native functions and APIs), data source leakage via hyperlink and image rendering behaviors, an XS-leak using frame counting/timing oracles, and a “denial of wallet” scenario targeting BigQuery cost exposure. Google remediated the vulnerabilities following responsible disclosure (reported as June 2025), and both sources state there is no evidence of in-the-wild exploitation at the time of publication.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Tenable publicly disclosed the nine 'LeakyLooker' vulnerabilities, describing zero-click and one-click cross-tenant attack paths in Google Looker Studio. The disclosure said there was no evidence of exploitation in the wild and detailed impacts including arbitrary SQL queries, data leakage, XS-Leaks, and BigQuery 'denial of wallet' abuse.
Google fixed all reported LeakyLooker issues in its Google-managed Looker Studio service after receiving Tenable’s disclosure. Reports said customers did not need to apply patches themselves because the remediation was performed service-side.
Tenable reported nine cross-tenant vulnerabilities in Google Looker Studio to Google through responsible disclosure. The flaws affected Looker Studio’s connector and credential model and could enable cross-tenant SQL execution, data exfiltration, data tampering, and cost-amplification attacks.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Tenable disclosed two vulnerabilities in **Google Looker** (collectively dubbed **“LookOut”**) that can enable **remote code execution (RCE)** and **sensitive data exposure**, with heightened risk for organizations running **customer-hosted/on-premises** Looker. Tenable reported an RCE chain involving **Git hook overrides** that could allow attackers to execute arbitrary commands on the Looker host, potentially leading to full server compromise, theft of secrets, data manipulation, and lateral movement into internal networks; in Google-hosted environments, the technique was described as having potential **cross-tenant** impact by bypassing isolation controls. A second issue (tracked as **CVE-2025-12743**) enables **exfiltration of Looker’s internal management database** by abusing internal connection behavior, allowing attackers to extract sensitive configuration data and credentials. Google has already remediated the issues in its **managed Looker (SaaS) on Google Cloud**, but **self-hosted deployments remain exposed until patched**, with guidance to upgrade to fixed releases (including `25.12.30+`, `25.10.54+`, `25.6.79+`, `25.0.89+`, `24.18.209+`), and clarification that **Looker Studio** is not affected.
Jun 29, 2026
Metabase disclosed a **critical unauthenticated SQL injection zero-day** affecting `1.58+` that was actively exploited against Metabase Cloud tenants and vulnerable self-hosted deployments. The company said the flaw could give remote attackers administrator access and enable theft of stored database credentials and accessible data; it has since blocked the attack paths and released fixes. Metabase rated the issue `CVSS 10.0` and urged self-hosted customers to upgrade, revoke sessions, rotate credentials, and review logs for signs of compromise. The downstream impact has already hit multiple organizations. Framework told customers that attackers breached its Metabase-hosted cloud instance through the upstream provider and stole personal data affecting **all customers**, including names, email addresses, phone numbers, and physical addresses, but not payment information. Tally separately said an attacker accessed its Metabase analytics service and obtained user email addresses and password hashes, while stating that forms and submitted responses were stored separately and were not accessed. LexisNexis also reported disruption and unusual activity involving systems connected to its Metabase API through a third-party vendor.
Sep 3, 2026
Metabase disclosed and patched multiple critical vulnerabilities after a zero-day was exploited against **Metabase Cloud**, prompting urgent warnings for organizations running self-hosted instances. The flaws include two unauthenticated SQL injection issues, `CVE-2026-72898` and `CVE-2026-72899`, and a missing authorization vulnerability, `CVE-2026-72900`. According to the advisories, `CVE-2026-72898` can be abused through the `/reset_password` database endpoint to obtain administrator-level access, and both SQL injection bugs are reported as actively exploited. Metabase said its cloud service was patched for customers, while national cybersecurity authorities urged self-hosted users to update immediately. Affected releases earlier than **63.5, 62.9, 61.11, 60.17, 59.21, and 58.24** should be upgraded to those fixed versions or later across the supported `0.58.x` to `0.63.x` branches. The notices emphasize prompt remediation because the vulnerabilities allow remote, unauthenticated compromise of exposed Metabase deployments.
Aug 12, 2026