Description
Inappropriate implementation in Input in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)
Published: 2026-05-28
Score: 5.8 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A crafted HTML page exploits an inappropriate input handling routine in Google Chrome for Android, exposing weaknesses identified as CWE‑284, CWE‑305, and CWE‑653. These flaws enable an attacker who has already compromised the renderer process to bypass the browser’s site isolation safeguards. The resulting privilege escalation permits the attacker to read, modify, or inject data across rendering contexts that are normally separated, creating a pathway to cross‑site data theft or credential compromise. Chromium classifies the vulnerability as High severity.

Affected Systems

The flaw exists in Google Chrome for Android versions prior to 148.0.7778.216. Devices running any earlier version are susceptible until the next update is installed.

Risk and Exploitability

No public exploit has been disclosed, and the EPSS score is below 1%, indicating very low observed exploitation probability. The vulnerability is not listed in CISA KEV. However, it requires the attacker to first gain control of the renderer process, which could occur through other browser or system weaknesses. Once that condition is met, bypassing site isolation offers significant opportunities for further attacks within the browser session. The CVSS score of 5.8 reflects a moderate‑to‑high impact for an affected user.

Generated by OpenCVE AI on May 29, 2026 at 15:47 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update Chrome for Android to version 148.0.7778.216 or later, which applies the fixed input handling logic.
  • If an immediate update is not feasible, disable or restrict third‑party sites from running in separate renderer processes by using browser flags or policy‑based isolation settings.
  • Consider switching to a browser implementation that enforces stricter isolation until Chrome can be upgraded, or restrict the device’s network access to reduce the likelihood of remote content triggers.

Generated by OpenCVE AI on May 29, 2026 at 15:47 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 29 May 2026 16:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-284
CWE-305

Fri, 29 May 2026 12:15:00 +0000

Type Values Removed Values Added
Title Chrome Android Site Isolation Bypass via Crafted HTML chromium-browser: Inappropriate implementation in Input
Weaknesses CWE-653
References
Metrics threat_severity

None

cvssV3_1

{'score': 5.8, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:N/A:N'}

threat_severity

Important


Thu, 28 May 2026 23:45:00 +0000

Type Values Removed Values Added
Title Chrome Android Site Isolation Bypass via Crafted HTML
First Time appeared Google
Google chrome
Weaknesses CWE-284
CWE-305
Vendors & Products Google
Google chrome

Thu, 28 May 2026 22:45:00 +0000

Type Values Removed Values Added
Description Inappropriate implementation in Input in Google Chrome on Android prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: High)
References

cve-icon MITRE

Status: PUBLISHED

Assigner: Chrome

Published:

Updated: 2026-05-28T22:25:54.027Z

Reserved: 2026-05-28T17:25:13.604Z

Link: CVE-2026-10010

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-05-28T23:16:42.840

Modified: 2026-05-29T02:36:13.047

Link: CVE-2026-10010

cve-icon Redhat

Severity : Important

Publid Date: 2026-05-27T00:00:00Z

Links: CVE-2026-10010 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-05-29T16:00:15Z

Weaknesses