SQL Injection in Looker Project Generation Endpoint Allows Access to Internal MySQL Database

Summary

The Looker endpoint for generating new projects from database connections allows users to specify "looker" as a connection name, which is a reserved internal name for Looker's internal MySQL database. The schemas parameter is vulnerable to SQL injection, enabling attackers to manipulate SELECT queries that are constructed and executed against the internal MySQL database. This vulnerability allows users with developer permissions to extract data from Looker's internal MySQL database. Looker-hosted and Self-hosted were found to be vulnerable. This issue has already been mitigated for Looker-hosted instances. No user action is required for these. Self-hosted instances must be upgraded as soon as possible. This vulnerability has been patched in all supported versions of Self-hosted. The versions below have all been updated to protect against this vulnerability. You can download these versions at the Looker download page https://download.looker.com/ : • 24.12.106 • 24.18.198+ • 25.0.75 • 25.6.63+ • 25.8.45+ • 25.10.33+ • 25.12.1+ • 25.14+

Timeline

1. Nov 19, 2025, 4:41 PM UTCCVE published
2. Nov 19, 2025, 6:47 PM UTCCISA SSVC assessment

   Exploitation: none · Automatable: no · Technical impact: partial

3. Nov 19, 2025, 6:47 PM UTCRecord last updated

Affected versions

• Google Cloud Looker

  fixed in 24.12.106; fixed in 24.18.198; fixed in 25.0.75; fixed in 25.6.63; fixed in 25.8.45; fixed in 25.10.33; fixed in 25.12.1; fixed in 25.14

• Google Cloud Looker

  fixed in 24.12.106; fixed in 24.18.198; fixed in 25.0.75; fixed in 25.6.63; fixed in 25.8.45; fixed in 25.10.33; fixed in 25.12.1; fixed in 25.14

References 2