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

CVE-2026-13934: Google Chrome RCE Vulnerability

CVE-2026-13934 is a remote code execution flaw in Google Chrome on Android that enables sandbox escape through crafted HTML pages. This article covers the technical details, affected versions, and mitigations.

Published:

CVE-2026-13934 Overview

CVE-2026-13934 is an input validation vulnerability in the Dawn component of Google Chrome on Android. Dawn is Chrome's cross-platform implementation of the WebGPU standard. The flaw affects Chrome versions prior to 150.0.7871.47 and allows a remote attacker who has already compromised the renderer process to potentially escape the Chrome sandbox using a crafted HTML page. Successful exploitation gives the attacker code execution outside the renderer's restricted context, expanding access to the underlying Android device. Google classified the Chromium security severity as Medium, while the NVD scoring reflects the high impact of a sandbox escape.

Critical Impact

A crafted HTML page can chain with a prior renderer compromise to escape the Chrome sandbox on Android, enabling execution outside the renderer's isolation boundary.

Affected Products

  • Google Chrome on Android prior to 150.0.7871.47
  • Chromium-based browsers on Android that embed the vulnerable Dawn/WebGPU implementation
  • Downstream distributions shipping unpatched Chromium builds

Discovery Timeline

  • 2026-06-30 - CVE-2026-13934 published to NVD
  • 2026-07-01 - Last updated in NVD database

Technical Details for CVE-2026-13934

Vulnerability Analysis

The vulnerability resides in Dawn, the component that implements WebGPU inside Chrome. Dawn receives commands from web content executing in the renderer process and forwards them to the GPU process, which has higher privileges than the sandboxed renderer. This vulnerability is classified as improper input validation [CWE-20].

Attackers cannot exploit this issue directly from a normal renderer boundary. The advisory states the attacker must have already compromised the renderer process. From that foothold, malformed WebGPU commands crossing the Dawn interface can bypass validation and reach the GPU process with unintended state. The result is a sandbox escape, giving the attacker execution in a process outside the renderer's restrictions.

Root Cause

The root cause is insufficient validation of untrusted input processed by Dawn. Commands or parameters supplied from the renderer are trusted or interpreted incorrectly before being handed to the more privileged GPU process. The renderer sandbox assumes the interprocess boundary enforces validation, and this assumption fails in the vulnerable code path.

Attack Vector

Exploitation is a two-stage chain. First, the attacker compromises the renderer using a separate vulnerability, typically delivered through a crafted HTML page. Second, from the compromised renderer, the attacker issues malformed Dawn/WebGPU calls to break out of the sandbox. User interaction is required to visit or load the malicious page. Verified public proof-of-concept code is not available. See the Chromium Issue Tracker Entry and Google Chrome Stable Update for technical details.

Detection Methods for CVE-2026-13934

Indicators of Compromise

  • Chrome for Android processes with versions earlier than 150.0.7871.47 remaining active after the patch release
  • Unexpected child process activity spawned from Chrome's GPU process on Android endpoints
  • Renderer or GPU process crashes correlated with visits to untrusted pages that use WebGPU

Detection Strategies

  • Inventory installed Chrome versions across managed Android fleets and flag builds below 150.0.7871.47
  • Monitor mobile threat telemetry for anomalous Chrome GPU process behavior, including unexpected memory regions or native library loads
  • Correlate browser crash reports with URL history to identify pages triggering renderer or GPU faults

Monitoring Recommendations

  • Ingest Chrome update and version telemetry into a central logging platform to track patch compliance
  • Alert on repeated Chrome renderer or GPU crashes originating from the same origin or session
  • Watch for post-exploitation indicators on Android, including unauthorized network egress from the browser process

How to Mitigate CVE-2026-13934

Immediate Actions Required

  • Update Google Chrome on Android to 150.0.7871.47 or later on every managed device
  • Enforce automatic Chrome updates through mobile device management policies
  • Identify and remediate any Chromium-based Android browsers that embed a vulnerable Dawn build

Patch Information

Google addressed CVE-2026-13934 in Chrome 150.0.7871.47 for Android. Details of the release are documented in the Google Chrome Stable Update advisory, and the underlying issue is tracked in the Chromium Issue Tracker Entry. Apply the vendor update; no supported configuration change replaces the patch.

Workarounds

  • Restrict access to untrusted websites on Android devices until patching is complete
  • Disable WebGPU in Chrome via enterprise policy where the feature is not required by business workflows
  • Segment high-risk mobile users and require them to browse only vetted sites until updates are verified
bash
# Verify installed Chrome version on Android via adb
adb shell dumpsys package com.android.chrome | grep versionName

# Expected output should show 150.0.7871.47 or later

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

Default Legacy - Prefooter | Experience the World’s Most Advanced Cybersecurity Platform

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.