CVE-2025-12739: Google Cloud Looker · XSS or 'Cross-site Scripting'
Affects Google Cloud LookerSource CVE Database V5
Not known to be exploited · CVSS 7.3 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/U:RedExploitation evidence
Disclosed: evidence found.
CVE published 24 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Google Cloud Looker | Affected
| Fixed in– |
AI-suggested
European organizations should immediately identify whether they operate self-hosted Looker instances and verify the installed version. If running vulnerable versions prior to 24.18.201 or the listed patched releases, they must prioritize upgrading to the latest patched versions available from the official Looker download page. Additionally, organizations should audit installed Looker extensions and disable any unnecessary or untrusted extensions to reduce the attack surface. Implement strict access controls and monitor viewer-level accounts for suspicious activity, as these accounts can be leveraged to craft malicious URLs. Educate Looker administrators about the risk of opening untrusted URLs, especially those received via email or messaging platforms. Employ web filtering and email security solutions to detect and block phishing attempts that might deliver malicious URLs. Finally, consider implementing Content Security Policy (CSP) headers and other browser-based mitigations to limit the impact of potential XSS attacks within the Looker environment.
Description
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. 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.18.201+ * 25.0.79+ * 25.6.66+ * 25.12.7+ * 25.16.0+ * 25.18.0+ * 25.20.0+