Looker is widely used enterprise analytics; XSS enabling admin takeover can disrupt data access and operations across organizations.
CVE-2026-15810
XSS in Google Looker via crafted URL enabling JS execution and admin takeover.
Is CVE-2026-15810 being exploited?
Not confirmed. CVE-2026-15810 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-15810?
CVE-2026-15810 is rated High with a CVSS score of 8.7. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-15810?
Yes. A fix has been recorded for CVE-2026-15810. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15810 affect?
CVE-2026-15810 affects Google Cloud Looker (self-hosted) versions prior to 25.6.103, 25.12.65, 25.18.68, 26.0.66, 26.2.47, 26.4.36, 26.6.28, 26.8.7, Google Cloud Looker (hosted) - mitigated (no action required). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15810?
Upgrade self-hosted Looker to the listed patched versions immediately and review admin accounts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Arbitrary JavaScript execution via malicious URL can hijack admin sessions, escalate privileges, and enable full Looker account takeover.
Immediate action required
- affected< 25.6.103
- affected< 25.12.65
- affected< 25.18.68
- affected< 26.0.66
- affected< 26.2.47
- affected< 26.4.36
- affected< 26.6.28
- affected< 26.8.7
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.