CVE-2026-17713 Google CVE debrief

Who should care

Users of Google Chrome on Android, particularly those with high-risk exposure to untrusted HTML pages, should be aware of this vulnerability. This includes organizations and individuals who use Google Chrome on Android for browsing or other purposes, as well as security teams and vulnerability management teams who need to assess and mitigate the risk of this vulnerability. Additionally, operators of Android devices and platforms that use Google Chrome should review and apply patches as necessary to prevent exploitation.

Technical summary

Insufficient validation of untrusted input in Accessibility in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. This vulnerability is a result of inadequate input validation in the Accessibility feature of Google Chrome on Android, which can be exploited by a remote attacker to escape the sandbox. The vulnerability has a high severity according to Chromium security and a CVSS score of 9.6.

Defensive priority

Critical vulnerability in Google Chrome on Android, allowing potential sandbox escape via crafted HTML page.

Recommended defensive actions

• Apply patch to Google Chrome on Android to version 151.0.7922.72 or later
• Restrict access to untrusted HTML pages
• Monitor for suspicious activity in renderer processes
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

Insufficient validation of untrusted input in Accessibility in Google Chrome on Android prior to 151.0.7922.72. High severity according to Chromium security. CVSS score of 9.6. The vulnerability allows a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. Evidence is limited to public sources and may not reflect the full scope of affected systems or potential impact. Defenders should verify patch deployment, review renderer process isolation, and monitor for suspicious activity.

Official resources