Skip to main content
Vulnerability Database/CVE-2026-102303

CVE-2026-102303: Google Chrome GPU XSS Vulnerability

CVE-2026-102303 is a cross-site scripting vulnerability in Google Chrome's GPU component on Android that allows remote attackers to obtain cross-origin data. This post explains its impact, affected versions, and mitigation steps.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-102303 Overview

CVE-2026-102303 is an uninitialized resource vulnerability in the GPU component of Google Chrome on Android prior to version 154.0.8037.92. A remote attacker can leverage a crafted HTML page to obtain cross-origin data, breaching the same-origin policy that isolates web content. Chromium classifies the security severity as High, while the assigned CVSS score reflects lower confidentiality impact and required user interaction. The flaw is tracked under [CWE-908: Use of Uninitialized Resource].

Critical Impact

A remote attacker can read cross-origin data from a victim's browser by luring them to a malicious HTML page rendered on Android.

Affected Products

  • Google Chrome for Android prior to 154.0.8037.92
  • Chromium-based browsers on Android sharing the vulnerable GPU code path
  • Android WebView components downstream from the affected Chromium branch

Discovery Timeline

  • 2026-09-29 - CVE-2026-102303 published to the National Vulnerability Database (NVD)
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-102303

Vulnerability Analysis

The vulnerability resides in Chrome's GPU process, which handles hardware-accelerated rendering for web content including WebGL, canvas, and video textures. On Android, the GPU process allocates buffers and texture memory that back cross-origin resources during compositing. When these resources are not fully initialized before use, residual memory contents can be exposed to JavaScript running in an attacker-controlled origin.

Because the leak crosses the same-origin boundary, an attacker can read fragments of pixel data, textures, or framebuffer contents belonging to unrelated origins. The exploitation requires the victim to load a crafted HTML page, which is trivially satisfied through phishing, malvertising, or compromised sites.

Root Cause

The root cause is uninitialized resource usage in a GPU code path, categorized under [CWE-908]. Memory or GPU buffers are read or sampled before being explicitly zeroed or written with expected content. The stale bytes returned to the renderer can contain remnants of previously rendered cross-origin content.

Attack Vector

Exploitation occurs over the network with low complexity and no privileges required, but the victim must interact by visiting a malicious page. The attacker delivers HTML and JavaScript that instruct the GPU to allocate resources and read their contents through APIs such as WebGL readPixels or canvas getImageData. Refer to the Chromium Issue Tracker #559727039 for additional technical context.

// No verified proof-of-concept is publicly available.
// The vulnerability is triggered by a crafted HTML page that
// causes the GPU process to sample uninitialized graphics memory
// and returns cross-origin pixel data to the attacker's script.

Detection Methods for CVE-2026-102303

Indicators of Compromise

  • Android devices running Google Chrome versions prior to 154.0.8037.92
  • Browser telemetry showing visits to untrusted domains hosting WebGL or canvas-heavy content immediately preceding sensitive data exposure
  • Unexpected outbound POST traffic from Chrome on Android containing base64-encoded image or pixel data

Detection Strategies

  • Inventory installed Chrome versions across managed Android fleets and flag builds older than 154.0.8037.92
  • Correlate mobile browser telemetry with threat intelligence feeds to identify access to known malvertising or exploit-hosting domains
  • Monitor mobile device management (MDM) attestation reports for out-of-date Chrome application versions

Monitoring Recommendations

  • Enable MDM policies that report installed browser versions on enrolled Android endpoints
  • Log DNS and HTTP egress from mobile devices through a corporate secure web gateway where feasible
  • Alert on repeated cross-origin resource requests followed by large outbound data transfers from mobile browsers

How to Mitigate CVE-2026-102303

Immediate Actions Required

  • Update Google Chrome for Android to version 154.0.8037.92 or later through the Google Play Store
  • Push MDM configurations that enforce automatic browser updates on managed Android devices
  • Advise users to avoid opening untrusted links on Android until the update is applied

Patch Information

Google addressed CVE-2026-102303 in Chrome for Android 154.0.8037.92. Details are published in the Google Chrome Stable Update release notes. Android users receive the update through the Google Play Store; verify the installed version under Chrome's About menu.

Workarounds

  • Use an alternative browser on Android until the Chrome update is installed, recognizing that many alternatives share the Chromium engine
  • Restrict browsing on Android to trusted sites and disable JavaScript on untrusted origins where feasible
  • Deploy DNS filtering or a secure web gateway to block known malicious domains hosting exploit content
bash
# Verify Chrome for Android version via adb on a managed device
adb shell dumpsys package com.android.chrome | grep versionName

# Expected output should show 154.0.8037.92 or later

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.