CVE-2025-12740: Remote Command Execution in Looker via IBM DB2 JDBC drive
A Looker user with a Developer role could create a database connection using IBM DB2 driver and, by manipulating LookML, cause Looker to execute a malicious command, due to inadequate filtering of the driver's parameters.
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/ : 25.0.93+ 25.6.84+
25.12.42+ 25.14.50+ 25.16.44+
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-12740?
CVE-2025-12740 is considered a high-severity vulnerability due to its potential to allow execution of malicious commands.
How do I fix CVE-2025-12740?
To fix CVE-2025-12740, it is recommended to update Looker to the latest version that addresses this vulnerability.
What software versions are affected by CVE-2025-12740?
CVE-2025-12740 affects Looker versions 25.0.93, 25.6.84, 25.12.42, 25.14.50, and 25.16.44.
What types of installations are impacted by CVE-2025-12740?
Both Looker-hosted and self-hosted installations are impacted by CVE-2025-12740.
Who is at risk from CVE-2025-12740?
Looker users with a Developer role are at risk from CVE-2025-12740.