HarborGuard / CVE
Back to search
HIGHCVE-2026-9888Published Modified CNA Chrome

CVE-2026-9888: Use after free in WebView in Google Chrome on Android prior to 148

Use after free in WebView in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Critical)

HarborGuard Analysis

HarborGuard analysis

Synopsis

A use-after-free vulnerability exists in the WebView component of Google Chrome on Android, affecting all versions prior to 148.0.7778.216. The flaw is reachable over the network and requires no authentication, though it does require a victim to interact with attacker-controlled content and assumes the attacker has already compromised the renderer process. Successful exploitation enables a full sandbox escape, giving the attacker confidentiality, integrity, and availability impact beyond the browser's sandboxed process. A patched-image rebuild at version 148.0.7778.216 is available on HarborGuard for affected environments.

HarborGuard Coverage

Detection

Detection of CVE-2026-9888 is available across every HarborGuard environment, with the CVE matched against customer images within minutes of ingestion from upstream feeds, including custom-built Android container images that bundle Chrome or WebView. Coverage extends to images in both customer registries and active CI/CD pipelines.

Available
Triage

HarborGuard is capable of scoring this CVE at 8.3 HIGH (CVSS v3.1) and weighting that score against each environment's compliance policy to determine urgency. Triage routing routes findings to the appropriate team inbox within each customer organization based on policy configuration.

Available
Patch

A patched-image rebuild at Chrome 148.0.7778.216 is available on HarborGuard for any environment running an affected version. For customers with auto-remediation enabled, HarborGuard can perform the rebuild, run regression tests, and open a pull request against affected workloads automatically.

Available

Exploit Conditions

  • Network reachabilityRequired

    The attacker delivers the exploit over the network, requiring the victim's device to reach an attacker-controlled web resource.

  • AuthenticationNot required

    No account or credential is needed; the attacker interacts with the target entirely through a crafted web page.

  • Victim interactionRequired

    The victim must navigate to or otherwise load an attacker-crafted HTML page, requiring a social-engineering step to direct the victim to malicious content.

  • Attack complexityDetail

    Exploitation is rated high complexity because it requires the attacker to have already compromised the renderer process before the use-after-free sandbox escape can be triggered, introducing a meaningful pre-condition beyond simply serving a page.

Blast Radius

  • An attacker who triggers the sandbox escape reads data outside the WebView sandbox boundary, including session tokens, credentials, and application data stored by other processes.
  • The attacker gains the ability to write or modify data accessible to the host process, including files, shared storage, and application state.
  • The attacker can crash or destabilize processes outside the sandbox, causing the host application or dependent services to become unavailable.
  • Because the scope is changed (S:C in the CVSS vector), impact extends beyond the browser process itself to other components sharing the Android device environment.

How HarborGuard Handles This

Available on HarborGuard: detection of CVE-2026-9888 is matched against customer images at ingest time, covering registries and pipeline stages. Because a fix exists at Chrome 148.0.7778.216, a patched-image rebuild is available for any environment where an affected image is identified. For customers with auto-remediation enabled, HarborGuard can rebuild the image at the patched version, execute the configured regression-test suite, and open a pull request against affected workloads; for high-severity issues, median time from CVE publication to merged patch PR is around 90 minutes in environments with auto-remediation enabled. Where compliance policy requires manual approval before remediation, HarborGuard surfaces the finding with CVSS context and fix-version detail to the appropriate team inbox for review. Given the sandbox-escape impact and the renderer-compromise pre-condition, teams running Chrome or WebView in containerized Android environments should treat this as high-priority and verify rebuild completion promptly.

See how HarborGuard automates this

Metrics

CVSS v3.1
8.3
Severity
HIGH
Fixed in
148.0.7778.216
Affected Products
1

Fix available

148.0.7778.216
Affected packages
  • Google / Chrome
    < 148.0.7778.216 (from 148.0.7778.216)
CVSS Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H