Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-15810 – XSS Leading to Administrative Account Takeover – Google Cloud Looker (Self-Hoste…

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-15810 is a reflected Cross-Site Scripting (XSS) vulnerability in Google Cloud Looker affecting both Looker-hosted and self-hosted deployments. An unauthenticated attacker can craft a malicious URL that, when opened by a Looker administrator, executes arbitrary JavaScript in the administrator’s session and results in full administrative account takeover. The vulnerability carries a CVSS v4.0 base score of 8.7 (HIGH) and was disclosed by Google on July 22, 2026.

Technical details

  • Root cause: Improper neutralization of user-supplied input during web page generation (CWE-79); attacker-controlled data is reflected unsanitized into the Looker web interface and executed as JavaScript in the victim’s browser.
  • Trigger conditions: A Looker administrator must open a maliciously crafted URL supplied by the attacker — a standard prerequisite for reflected XSS, commonly delivered via phishing, embedded links, or social engineering.
  • Attack vector: Network-accessible (AV:N); the attacker requires no prior authentication or existing account on the Looker instance (PR:N).
  • Impact: Arbitrary JavaScript execution within the context of the administrator’s authenticated session, enabling full administrative account takeover — including access to all Looker data, dashboards, user accounts, and credentials for connected database sources.

Affected software

  • Google Cloud Looker (self-hosted): All 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
  • Google Cloud Looker (Looker-hosted / Google-managed SaaS): Was also affected; Google has automatically applied mitigations — no user action required for these instances.

Severity

CVSS v4.0 Base Score: 8.7 (HIGH)
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/U:Amber

Mitigation and recommended actions

  • Immediate action (self-hosted instances): Upgrade to a patched release on your active version branch:
    • 25.6.x → 25.6.103 or later
    • 25.12.x → 25.12.65 or later
    • 25.18.x → 25.18.68 or later
    • 26.0.x → 26.0.66 or later
    • 26.2.x → 26.2.47 or later
    • 26.4.x → 26.4.36 or later
    • 26.6.x → 26.6.28 or later
    • 26.8.x → 26.8.7 or later
  • Looker-hosted (SaaS) instances: No action required — Google has already deployed mitigations automatically.
  • If immediate patching is not feasible: Restrict network access to self-hosted Looker instances via firewall rules or VPN so that only trusted internal users can reach the web interface. Additionally, instruct administrators not to open unexpected or unsolicited Looker URLs from external sources.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge