Looker vulnerabilities

In Looker configured with OIDC authentication, an attacker could take over a user account due to email address string normalization. Looker-hosted and Self-hosted were vulnerable; hosted is mitigated, self-hosted needs upgrade.

A Looker user with Developer role could create a database connection using Denodo driver and manipulate LookML to execute a malicious command. Looker-hosted and Self-hosted are vulnerable; hosted is mitigated, self-hosted needs upgrade.

A Looker user with Developer role could create a database connection using IBM DB2 driver and manipulate LookML to execute a malicious command due to inadequate filtering. Looker-hosted and Self-hosted are vulnerable; hosted is mitigated, self-hosted needs upgrade.

An attacker with viewer permissions in Looker could craft a malicious URL that, when opened by a Looker admin, would execute an attacker-supplied script. Exploitation required at least one Looker extension installed on the instance.

A Command Injection vulnerability, resulting from improper file path sanitization (Directory Traversal) in Looker allows an attacker with Developer permission to execute arbitrary shell commands when a user is deleted on the host system. 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 from this vulnerability. You can download these versions at the Looker download page https://download.looker.com/ : 24.12.100+, 24.18.192+, 25.0.69+, 25.6.57+, 25.8.39+, 25.10.22+