PatchSiren cyber security CVE debrief
CVE-2026-15810 Google Cloud CVE debrief
A Cross-Site Scripting (XSS) vulnerability was discovered in Google Cloud Looker versions prior to 25.6.103, 25.12.65, 25.18.68, 26.0.66, 26.2.47, 26.4.36, 26.6.28, and 26.8.7. This vulnerability allows an attacker to execute arbitrary JavaScript, potentially leading to administrative account takeover, using a maliciously crafted URL. The vulnerability impacts both Looker-hosted and self-hosted instances, although Looker-hosted instances have already been mitigated. Self-hosted instances require an upgrade to patched versions: 25.6.103+, 25.12.65+, 25.18.68+, 26.0.66+, 26.2.47+, 26.4.36+, 26.6.28+, or 26.8.7+. It is essential for administrators and users of Google Cloud Looker, especially those with self-hosted instances, to be aware of this vulnerability and take necessary actions to mitigate it.
- Vendor
- Google Cloud
- Product
- Looker
- CVSS
- HIGH 8.7
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-07-24
- Original CVE updated
- 2026-07-27
- Advisory published
- 2026-07-24
- Advisory updated
- 2026-07-27
Who should care
Administrators and users of Google Cloud Looker, especially those with self-hosted instances, should be aware of this vulnerability and take necessary actions to mitigate it. This includes upgrading self-hosted instances to the patched versions and reviewing and monitoring Looker instance logs for suspicious activity.
Technical summary
The CVE-2026-15810 vulnerability is a Cross-Site Scripting (XSS) issue affecting Google Cloud Looker. It allows attackers to execute arbitrary JavaScript code via a maliciously crafted URL, potentially leading to administrative account takeover. The vulnerability impacts both Looker-hosted and self-hosted instances, although Looker-hosted instances have already been mitigated. Self-hosted instances require an upgrade to patched versions: 25.6.103+, 25.12.65+, 25.18.68+, 26.0.66+, 26.2.47+, 26.4.36+, 26.6.28+, or 26.8.7+.
Defensive priority
High
Recommended defensive actions
- Upgrade self-hosted Google Cloud Looker instances to patched versions: 25.6.103+, 25.12.65+, 25.18.68+, 26.0.66+, 26.2.47+, 26.4.36+, 26.6.28+, or 26.8.7+.
- Review and monitor Looker instance logs for suspicious activity.
- Implement additional security measures, such as input validation and output encoding, to prevent similar attacks.
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
- Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.
- Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.
- Check relevant monitoring, detection, and logs for exposed assets that need extra review.
Evidence notes
The CVE record was published on 2026-07-24T12:16:47.543Z and was last modified on 2026-07-27T20:37:16.927Z. The NVD entry is currently Awaiting Analysis. This information is based on the supplied source corpus. Further verification is recommended to confirm the accuracy of this information.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-15810 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-15810
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-15810 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-15810
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://docs.cloud.google.com/looker/docs/release-notes
f45cbf4e-4146-4068-b7e1-655ffc2c548c
-
Source reference
Unverified legacy reference
URL: https://docs.cloud.google.com/support/bulletins
f45cbf4e-4146-4068-b7e1-655ffc2c548c
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.