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

CVE-2026-10934 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-10934?

A high-severity vulnerability in Google Chrome for Android (CVE-2026-10934, CVSS 8.3) threatens device security across your mobile-enabled organization.. A patch is available.

How to fix or mitigate CVE-2026-10934?

Within 24 hours: Scan for Android devices running Chrome versions prior to 149.0.7827.53. Within 7 days: Push Chrome version 149.0.7827.53 or later to all affected devices through your MDM solution. Within 30 days: Confirm patch deployment across 100% of Android devices and validate no vulnerable versions remain.

Google Chrome CVE-2026-10934

EUVD-2026-34383 HIGH

Use After Free (CWE-416)

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

GHSA-w4c6-rrw4-6w3q

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

8.8 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:42 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 Autofill 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 prior to 149.0.7827.53 allows a remote attacker who already controls the renderer process to break out of the browser sandbox via a crafted HTML page that triggers a use-after-free in the Autofill component. Chromium rates the severity High and a vendor patch is available; no public exploit identified at time of analysis and the issue is not listed in CISA KEV.

Technical ContextAI

The flaw is a CWE-416 use-after-free in Chrome's Autofill subsystem on Android. Autofill runs in the browser process and handles form-field suggestions sourced from saved profiles and payment data; when the renderer interacts with it through Mojo IPC, freed C++ objects can be referenced again, yielding an attacker-controlled dangling pointer that is reachable from a compromised renderer. Because Autofill code executes outside the renderer sandbox, corrupting its memory provides a path to escalate from renderer RCE (typically obtained through a prior bug) into the higher-privileged browser process, undermining Chrome's site-isolation and sandbox boundary on Android (Chromium issue 501594107).

RemediationAI

Vendor-released patch: Google Chrome for Android 149.0.7827.53 or later - update via Google Play or the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. Because exploitation requires a pre-existing compromised renderer plus user interaction with a crafted page, interim compensating controls for fleets that cannot immediately update include disabling Autofill for addresses and payment methods in chrome://settings/autofill (reduces the attack surface of the vulnerable component at the cost of user convenience), and enforcing managed-browser policies such as AutofillAddressEnabled=false and AutofillCreditCardEnabled=false via Android enterprise MDM. Restricting users to known-good sites via SafeBrowsing Enhanced Protection and URL allowlists further limits exposure to attacker-controlled HTML, though it does not address the underlying memory-corruption bug.