CVE-2026-17727 Google CVE debrief

Who should care

Google Chrome users on Android, cybersecurity teams responsible for browser security, and IT teams managing Chrome deployments should be aware of this vulnerability. They should review the official CVE and NVD records, assess their exposure, and plan for updates or mitigations. Security teams should also monitor for suspicious activity and review compensating controls for exposed systems.

Technical summary

Out of bounds write in WebGL in Google Chrome on Android prior to 151.0.7922.72 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. The vulnerability has a high severity score of 9.6 and is classified as CRITICAL. It affects Google Chrome users on Android. There is no information on known or potential exploits. The vulnerability is caused by an out-of-bounds write issue in WebGL, which can be triggered by a crafted HTML page. Defenders should verify affected product deployments, review official advisories, and plan for vendor-supported updates or mitigations. Limited details on exploitation are available, emphasizing the need for defenders to focus on patching and compensating controls.

Defensive priority

Critical vulnerability in Google Chrome on Android, requiring immediate attention due to potential sandbox escape.

Recommended defensive actions

• Apply Google Chrome update to version 151.0.7922.72 or later
• Restrict access to untrusted HTML pages
• Monitor for suspicious activity
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Review compensating controls for exposed systems while remediation is scheduled and verified

Evidence notes

Official CVE and NVD records confirm the vulnerability. Google Chrome on Android versions prior to 151.0.7922.72 are affected. Limited details on exploitation. The vulnerability has a high severity score of 9.6 and is classified as CRITICAL. There is no information on known or potential exploits. Defenders should verify affected product deployments, review official advisories, and plan for vendor-supported updates or mitigations.

Official resources