What is the CVSS score of CVE-2026-10953?

CVE-2026-10953 has a CVSS 3.1 base score of 8.3 (High). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Google Chrome are affected by CVE-2026-10953?

Google Chrome on Android versions prior to 149.0.7827.53 contains a sandbox escape vulnerability that allows attackers to achieve complete device compromise following an initial browser renderer…. A patch is available.

How to fix or mitigate CVE-2026-10953?

Within 24 hours: Identify all Android devices running Chrome versions below 149.0.7827.53 in your device inventory and enable automatic updates if not already enabled. Within 7 days: Deploy Chrome version 149.0.7827.53 or later across all organizational Android devices through mobile device management (MDM) policies or user communication. Within 30 days: Verify patch compliance through device inventory audit and establish continuous monitoring for Chrome version management on all Android endpoints.

Google Chrome CVE-2026-10953

EUVD-2026-34402 HIGH

Use After Free (CWE-416)

2026-06-04 chrome-cve-admin@google.com

GHSA-v54j-r4vm-9pcv

Denial Of Service Google Use After Free Memory Corruption

8.3

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

8.3 HIGH

AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H

SUSE

HIGH

qualitative

Red Hat

9.0 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 05, 2026 - 02:50 vuln.today

CVSS changed

Jun 05, 2026 - 02:22 NVD

8.3 (HIGH)

CVE Published

Jun 04, 2026 - 23:16 nvd

HIGH 8.3

CVE Published

Jun 04, 2026 - 23:16 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

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)

AnalysisAI

Sandbox escape in Google Chrome on Android versions prior to 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via a crafted HTML page. The flaw stems from a use-after-free condition in the Core component and is rated High severity by Chromium with a CVSS of 8.3. No public exploit identified at time of analysis, though the bug enables a critical post-exploitation chain step when paired with a renderer RCE.

Technical ContextAI

The vulnerability resides in the Core component of Chromium, the foundational layer underlying Chrome's rendering and browser process logic. CWE-416 (Use After Free) indicates that memory is referenced after it has been freed, allowing an attacker to manipulate the freed object - typically by reallocating controlled data at the same address - to corrupt program state, hijack control flow, or escape isolation boundaries. Because the bug is reachable from a compromised renderer and affects the Android port of Chrome (CPE-equivalent: cpe:2.3:a:google:chrome:*:*:*:*:*:android), successful exploitation crosses the renderer-to-browser-process trust boundary, which is precisely the sandbox boundary Chrome relies on to contain web-originated code.

RemediationAI

Vendor-released patch: Google Chrome for Android 149.0.7827.53 - update via Google Play Store immediately, prioritizing managed mobile devices through MDM-enforced minimum-version policies. Reference the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html and tracking issue https://issues.chromium.org/issues/506147564 for confirmation. If patching cannot be completed immediately on all devices, compensating controls include restricting Chrome on Android to known/trusted sites via enterprise URL allowlist policies (trade-off: breaks general browsing), enforcing Site Isolation (already default on Android Chrome) and Safe Browsing Enhanced Protection (modest performance/privacy trade-off), and discouraging use of Chrome on Android for sensitive workflows until patched. Disabling JavaScript globally would mitigate most renderer-side prerequisite bugs but breaks the modern web and is rarely acceptable.