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

CVE-2026-106199: Google Chrome Android Auth Bypass Flaw

CVE-2026-106199 is an authorization bypass flaw in Google Chrome on Android that allows attackers to bypass site isolation through a compromised renderer process. 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-106199 Overview

CVE-2026-106199 is an incorrect authorization vulnerability [CWE-863] in the Actor component of Google Chrome on Android. The flaw affects Chrome for Android versions prior to 155.0.8059.39. A remote attacker who has already compromised the renderer process can use a crafted HTML page to potentially bypass Chrome's site isolation boundary. Site isolation enforces separation between web origins at the process level, so a bypass weakens one of the browser's primary sandbox defenses. Google's Chromium team rated the Chromium security severity as Low.

Critical Impact

Attackers with a pre-compromised renderer process can bypass site isolation on Android Chrome, potentially accessing cross-origin content that should remain segregated.

Affected Products

  • Google Chrome for Android, versions prior to 155.0.8059.39
  • Chromium-based builds incorporating the vulnerable Actor component
  • Android devices running affected Chrome releases

Discovery Timeline

  • 2026-10-06 - CVE-2026-106199 published to NVD
  • 2026-10-06 - Last updated in NVD database

Technical Details for CVE-2026-106199

Vulnerability Analysis

The vulnerability resides in Chrome's Actor subsystem on Android. The Actor component performs authorization checks when mediating operations across browser processes. In affected versions, those checks are incorrect, allowing operations that should be rejected across origin or process boundaries. The condition requires prior compromise of a renderer process, which raises the exploitation bar but is a realistic step in multi-stage browser attacks. A crafted HTML page served to the compromised renderer triggers the authorization gap and enables site isolation bypass. See the Chromium Issue Tracker entry #517703787 and the Google Chrome Stable Update announcement for vendor details.

Root Cause

The defect is classified as [CWE-863] Incorrect Authorization. The Actor component evaluates permissions for an action but reaches an incorrect decision, granting access that violates Chrome's site isolation model. This represents a logic flaw rather than a memory corruption bug.

Attack Vector

Exploitation requires two conditions. First, the attacker must already control the renderer process, typically through a separate browser exploit. Second, the attacker serves a crafted HTML page that invokes the vulnerable Actor code path. On success, the attacker reads or influences content from origins hosted in other renderer processes, undermining the per-site process boundary.

No verified public exploit code is available. The vulnerability is described in prose because synthetic exploitation code is not warranted for a logic flaw with no published proof of concept.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2026-106199

Indicators of Compromise

  • Chrome for Android instances reporting a version string below 155.0.8059.39
  • Unexpected cross-origin data access patterns originating from a single renderer session
  • Browser crash telemetry or renderer process anomalies preceding suspicious network activity

Detection Strategies

  • Inventory Android fleet browser versions and flag devices running Chrome below 155.0.8059.39
  • Correlate web gateway logs with endpoint telemetry to identify Android browsers reaching known exploit staging pages
  • Monitor mobile endpoints for abnormal process behavior tied to the Chrome application sandbox

Monitoring Recommendations

  • Enforce browser version reporting through mobile device management (MDM) solutions
  • Alert on Android Chrome installations that fall behind the current stable channel release
  • Review mobile threat defense logs for crafted HTML delivery indicators and renderer compromise precursors

How to Mitigate CVE-2026-106199

Immediate Actions Required

  • Update Google Chrome for Android to version 155.0.8059.39 or later through the Google Play Store
  • Push mandatory browser updates to managed Android devices via MDM policy
  • Restrict installation of unmanaged browsers on corporate Android devices until updates are confirmed

Patch Information

Google addressed the issue in Chrome 155.0.8059.39 on the stable channel. Refer to the Google Chrome Stable Update announcement for release notes and the Chromium Issue Tracker #517703787 for issue status.

Workarounds

  • No vendor-supplied workaround exists; apply the Chrome update as the primary remediation
  • Reduce exposure by limiting browsing of untrusted sites on Android devices pending patch deployment
  • Enforce enterprise browsing policies that block known malicious domains at the network edge
bash
# Verify Chrome for Android version via ADB
adb shell dumpsys package com.android.chrome | grep versionName
# Expected output should show versionName=155.0.8059.39 or higher

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.