Skip to main content
CVE-2025-12740VulnerabilityPublished

A Looker user with a Developer role could create a database connection using IBM DB2 driver and, by manipulating

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-12740· High 7.7

Not known to be exploited · CVSS 7.7 High.

Data as of 16 Nov 2026, 01:28 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GoogleCloud)CVSS 4.07.7
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/U:Red

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

AI-suggested

Looker-hosted instances have already been mitigated by the vendor; no user action is required for these environments. Self-hosted Looker instances must be upgraded immediately to one of the patched versions: 25.0.93 or later, 25.6.84 or later, 25.12.42 or later, 25.14.50 or later, or 25.16.44 or later. Users should download the updated versions from the official Looker download page and apply the upgrade to remediate the vulnerability.

Description

A vulnerability in Looker allows a user with a Developer role to create a database connection using the IBM DB2 driver and manipulate LookML to execute malicious commands due to inadequate filtering of driver parameters. This affects both Looker-hosted and Self-hosted instances. The issue has been mitigated for Looker-hosted instances with no user action required. Self-hosted instances must be upgraded to patched versions to address the vulnerability.

References

Community reviews

Loading reviews…