CVE-2026-10934: Chrome Android Autofill Use-After-Free Sandbox Escape

Technical summary

CVE-2026-10934 is a use-after-free (CWE-416) vulnerability in Google Chrome's Autofill functionality on Android. Use-after-free flaws occur when code accesses memory that has already been freed, potentially allowing an attacker to manipulate that memory and execute arbitrary code. In this case, the vulnerability exists in the renderer process—the sandboxed component that processes HTML and JavaScript. An attacker who has already compromised the renderer can craft a malicious HTML page that triggers the use-after-free condition in Autofill, enabling a sandbox escape. The CVSS 3.1 score of 8.3 (HIGH) reflects the high impact to confidentiality, integrity, and availability, moderated by the requirement for user interaction and a compromised renderer as a prerequisite.

Business impact

This vulnerability represents a significant escalation risk in multi-stage attacks. While a renderer compromise is needed first, successful exploitation could allow attackers to move from a sandboxed browser context to the underlying Android operating system, potentially leading to unauthorized access to sensitive user data, installation of malware, or lateral movement within the device. For organizations where employees use Chrome on Android devices for corporate email, banking, or other sensitive applications, this vulnerability increases the risk profile of those devices. The requirement for prior renderer compromise means this is more likely to affect users who have already clicked on malicious links or installed compromised content, making it part of a broader attack chain rather than a standalone entry point.

Affected systems

Google Chrome on Android versions prior to 149.0.7827.53 are affected. The vulnerability does not impact Chrome on other platforms (Windows, macOS, Linux) based on the CVE description, which specifically mentions Android. Chrome on desktop operating systems may have their own separate Autofill implementations or mitigations. Android users running Chrome 149.0.7827.53 or later are protected.

Exploitability

Exploitation requires two conditions: (1) the attacker must first successfully compromise Chrome's renderer process, and (2) the user must then visit a crafted HTML page while using the compromised renderer. This two-stage requirement significantly limits exploitability in the wild compared to vulnerabilities that can be triggered by simply visiting a malicious site. However, the Chromium security team rated this as HIGH severity, suggesting the post-compromise capabilities are severe. There is currently no evidence of active exploitation (the vulnerability is not listed on the CISA Known Exploited Vulnerabilities catalog), but security teams should assume that skilled attackers will develop reliable exploits once the patch is widely available for comparison.

Remediation

Users and administrators should prioritize updating Google Chrome on Android to version 149.0.7827.53 or later as soon as possible. The patch specifically addresses the use-after-free condition in Autofill. Administrators managing Android devices through Mobile Device Management (MDM) solutions should deploy Chrome updates through their standard patch management workflow. Given the need for prior renderer compromise, complementary defenses include blocking malicious advertisements, enforcing secure browsing policies, and monitoring for signs of renderer exploitation.

Patch guidance

Update Google Chrome on Android to version 149.0.7827.53 or later. Users can check their Chrome version by opening the Chrome app, tapping the three-dot menu, and navigating to Settings > About Chrome, which will display the current version and automatically check for updates. For organizations managing Chrome through enterprise policies, verify that your Mobile Device Management (MDM) policy enforces automatic Chrome updates or deploy the patched version directly. Testing the update in a non-production environment first is recommended to ensure compatibility with line-of-business applications, though Chrome updates are generally low-risk. Confirm patch deployment by verifying that affected devices report Chrome 149.0.7827.53 or higher.

Detection guidance

Detection of active exploitation is difficult because the vulnerability requires prior renderer compromise and a follow-up malicious HTML page. Log aggregation systems monitoring Android devices should look for: (1) unexpected Chrome crashes or restarts, particularly in proximity to suspicious web browsing activity; (2) unusual process behavior or privilege escalation attempts following Chrome activity; (3) unexpected data access or network connections originating from non-Chrome processes shortly after Chrome usage. Memory dumps from affected devices may show artifacts of use-after-free conditions, but require forensic analysis. The most practical detection approach is to ensure all Chrome instances are updated to 149.0.7827.53 or later and monitor for other indicators of renderer compromise, such as malicious advertisements or drive-by download attempts.

Why prioritize this

This vulnerability merits high-priority patching due to its sandbox-escape capability and HIGH CVSS score (8.3), but should not be treated as critical because exploitation requires prior renderer compromise. Organizations should patch within their standard high-priority window (7–14 days for most enterprises) rather than implementing emergency response procedures. The absence of KEV listing and active exploitation reports suggests this is not yet being weaponized at scale, reducing immediate pressure, but the severe nature of sandbox escapes means delay risks. Prioritize devices used by high-value targets (executives, finance staff) or those frequently exposed to untrusted web content.

Risk score, explained

The CVSS 3.1 score of 8.3 (HIGH) reflects: Attack Vector (Network) — the attack is triggered over the network via a malicious webpage; Attack Complexity (High) — exploitation requires prior renderer compromise, a non-trivial condition; Privileges Required (None) — once the renderer is compromised, no additional privileges are needed; User Interaction (Required) — the user must visit the crafted page; Scope (Changed) — the impact extends beyond the vulnerable component (Autofill) to the entire system (sandbox escape); Confidentiality/Integrity/Availability (High) — successful exploitation compromises all three security properties. The score appropriately reflects the severity of a sandbox escape while accounting for the prerequisite renderer compromise.

Frequently asked questions