High-severity sandbox escape in Google Chrome for Android — widely deployed client software; could lead to remote code execution on corporate mobile devices.
CVE-2026-17727
Out-of-bounds write in Chrome WebGL on Android enabling sandbox escape.
Is CVE-2026-17727 being exploited?
Not confirmed. CVE-2026-17727 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.41% probability of exploitation in the next 30 days.
How severe is CVE-2026-17727?
CVE-2026-17727 is rated Critical with a CVSS score of 9.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-17727?
Yes. A fix has been recorded for CVE-2026-17727. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-17727 affect?
CVE-2026-17727 affects Google Chrome for Android <151.0.7922.72, Chromium-based browsers on Android with same WebGL engine. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-17727?
Update Chrome for Android to 151.0.7922.72+ immediately; restrict untrusted web content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote sandbox escape via crafted HTML/WebGL page in Chrome for Android, enabling potential arbitrary code execution.
Immediate action required
- affected< 151.0.7922.72
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.