Skip to main content
VulnerabilityPublished

CVE-2025-12742: A Looker user with a Developer role could cause Looker to execute a malicious command, due to

Source GCVE Database

0
Compare
Authoritative record:CVE-2025-12742· High 7.5

Not known to be exploited · CVSS 7.5 High.

Data as of 18 Nov 2026, 02:28 UTC

CVSS 4.0 base score
7.5High
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.5
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/U:Red

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 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 17 Nov 2026.

What to do

AI-suggested

Looker-hosted instances have been fully mitigated by the vendor; no user action is required. For Self-hosted instances, immediate upgrade to one of the patched versions listed (24.12.108+, 24.18.200+, 25.0.78+, 25.6.65+, 25.8.47+, 25.12.10+, or 25.14+) is necessary to remediate the vulnerability.

Description

A vulnerability in Looker allows a user with a Developer role to cause execution of malicious commands due to insecure processing of Teradata driver parameters. This affects both Looker-hosted and Self-hosted instances. Looker-hosted instances have already been mitigated with no user action required. Self-hosted instances must be upgraded to patched versions to address the issue.

References

Community reviews

Loading reviews…