Reflected Cross-Site Scripting in Google Cloud Looker Enables Administrative Account Takeover

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-15810?

CVE-2026-15810 is a vulnerability classified as Improper Neutralization of Input During Web Page Generation, affecting Looker (affected versions: < 25.6.103, < 25.12.65, and other affected versions). This vulnerability is rated High, with a CVSS score of 8.7. Current sources do not report this vulnerability as exploited.

Overview

Original source data

A Cross-Site Scripting (XSS) vulnerability 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 on Looker-hosted and Self-hosted allows an attacker to execute arbitrary JavaScript leading to administrative account takeover using a maliciously crafted URL. 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 to the 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+.

Affected products and scope

  • Looker-hosted: The affected facts list versions before 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. Google separately states that the issue has been mitigated for Looker-hosted instances and that customers do not need to take action; the public guidance does not express the current hosted status as a separate version boundary.
  • Self-hosted: Versions before 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 are identified as affected. Patched branches include 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 and all later versions.

Technical details

Google Cloud Looker contains a CWE-79 flaw in which attacker-controlled data is reflected into web page content without proper neutralization. An attacker can craft a malicious URL; when a Looker administrator opens it, the administrator's browser may execute arbitrary JavaScript in the Looker context. The technical data supplied with the record indicates network reachability, no attacker privileges required, and low attack complexity, but passive user interaction is required because an administrator must open the URL. Both Looker-hosted and Self-hosted deployments were identified as vulnerable in affected release branches, although Looker-hosted instances have been mitigated on the service side. The available public material does not identify the URL parameter, endpoint, rendering sink, or specific payload, so those implementation details should not be inferred.

Exploitability

The vulnerability can be reached remotely through a specially crafted URL. The attacker does not need prior Looker privileges, but an administrator must open the malicious URL in a browser. The record describes this as passive user interaction and identifies low attack complexity. The supplied record does not mark the issue as known exploited and does not identify a public exploit; those statuses do not prove that exploitation has never occurred. No specific campaign, victim, payload, or exploitation indicator is established by the reviewed evidence.

Technical impact

The documented technical outcome is arbitrary JavaScript execution in the administrator's browser context after the malicious URL is opened. This can lead to administrative account takeover and unauthorized actions within that account's permissions. Possible consequences include data exposure, configuration modification, or impact to instance availability, but the available evidence does not confirm a specific post-exploitation action. The vulnerability is not described as server-side code execution, and the evidence does not establish cross-tenant impact or effects beyond the affected instance.

Business impact

If an administrator opens a malicious URL on an exposed instance, an attacker may gain control of the administrator's authenticated browser context. Possible consequences include unauthorized access to data and administrative functions, configuration changes, or service disruption, depending on the account's permissions and the instance's scope. These are potential consequences of account compromise, not evidence that a particular data breach or unauthorized change occurred. The record does not document a confirmed compromise.

Remediation

  1. Looker-hosted: No customer action is required for this issue according to Google's guidance because mitigation has been applied on the service side.
  2. Self-hosted: Identify the release branch in use and upgrade to the corresponding patched version: 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 and all later versions.
  3. After upgrading, verify the actual running version on every instance and ensure that no Self-hosted node or environment remains on a release below its branch boundary.
  4. The reviewed guidance does not provide an alternative workaround for Self-hosted deployments. If an administrator may have opened a suspicious URL, follow the organisation's account-compromise procedure, including review of administrative sessions and changes to permissions or configuration.
  5. Do not treat URL filtering, log monitoring, or disabling an unnamed feature as a substitute for the confirmed upgrade path.

Detection

  1. Inventory every Looker deployment and distinguish Looker-hosted from Self-hosted instances.
  2. For Self-hosted deployments, verify the running release on each branch and compare it with the patched boundaries in affected_summary.
  3. Review proxy, gateway, and browser telemetry for unusual Looker URLs sent to or opened in administrative contexts. This is a precautionary review, not a Google-published IOC.
  4. Review administrative activity around any suspected malicious URL exposure for unexpected changes to configuration, permissions, accounts, or sessions.
  5. Do not treat the absence of suspicious log evidence as proof of safety; confirm exposure through inventory and version verification.
Sources (17)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.