CVE-2026-10953

chromium-browser: Use after free in Core

Published Jun 4, 2026 CVSS 3.1 · 8.3 High EPSS < 1% KEV · Not listed
Description
Use after free in Core in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

Analysis

AI-generated

Technical impact

The vulnerability is a use‑after‑free in the core component of Google Chrome on Android, affecting versions prior to 149.0.7827.53. The flaw can be triggered by a crafted HTML page. If an attacker can compromise the renderer process, they may use the freed memory to execute arbitrary code, effectively escaping the browser's sandbox and potentially gaining full system access. This corresponds to CWE‑416, a use‑after‑free weakness, and CWE‑825, a data‑leak vulnerability.

Affected Systems

Google Chrome for Android versions earlier than 149.0.7827.53 are susceptible. The issue is confined to the Android edition; other platforms or later releases are not affected. Devices running these versions and which allow arbitrary HTML to be loaded in the renderer process are at risk.

Risk and Exploitability

The flaw carries a high severity rating according to Chromium. The CVSS score is 8.3, indicating high severity. The EPSS score is 0.00068, or less than 1%, suggesting a very low probability that the vulnerability will be exploited in the wild. The attack requires an attacker already able to run malicious code in the renderer process, typically by serving a crafted web page. A successful sandbox escape would give the attacker full control over the device, bypassing browser isolation. Because the vulnerability is not listed in CISA’s KEV catalog, there is no current evidence of widespread exploitation, but the high severity and the possibility of remote code execution warrant urgent patching.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update Google Chrome to at least version 149.0.7827.53 to remove the use‑after‑free flaw
  • Ensure the device OS and related security patches are current to limit potential avenues for an attacker to compromise the renderer process
  • Disable or limit the loading of untrusted content in Chrome, for example by configuring safe browsing or restricting extensions, as a temporary measure until the patch is applied

Generated by OpenCVE AI on June 7, 2026 at 14:39 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Debian DSA Debian DSA DSA-6325-1 chromium security update
History
Type Values Removed Values Added
First Time appeared Google android
CPEs cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*
cpe:2.3:o:google:android:-:*:*:*:*:*:*:*
Vendors & Products Google android
Type Values Removed Values Added
Title chromium-browser: Use after free in Core
Weaknesses CWE-825
References
Metrics threat_severity

None

threat_severity

Important

Type Values Removed Values Added
Title Use‑After‑Free in Chrome Android Core Enables Potential Sandbox Escape
Type Values Removed Values Added
First Time appeared Google
Google chrome
Vendors & Products Google
Google chrome
Type Values Removed Values Added
Metrics cvssV3_1

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

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
Title Use‑After‑Free in Chrome Android Core Enables Potential Sandbox Escape
Type Values Removed Values Added
Description Use after free in Core in Google Chrome on Android prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
Weaknesses CWE-416
References
Weaknesses

Sources

Status
PUBLISHED
Assigner
Chrome
Published
Updated
Jun 5, 2026, 1:39 AM
Reserved
Jun 4, 2026, 5:06 PM
Status
Analyzed
Published
Jun 4, 2026, 11:16 PM
Modified
Jul 22, 2026, 8:10 PM
Severity
Important
Public date
Jun 2, 2026, 12:00 AM