Critical remote sandbox escape in Google Chrome on Android, a widely used browser; high-impact RCE risk across devices used in enterprises and consumers.
CVE-2026-19170
Use-after-free in WebGL in Chrome for Android enables sandbox escape.
Is CVE-2026-19170 being exploited?
Not confirmed. CVE-2026-19170 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.38% probability of exploitation in the next 30 days.
How severe is CVE-2026-19170?
CVE-2026-19170 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-19170?
Yes. A fix has been recorded for CVE-2026-19170. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-19170 affect?
CVE-2026-19170 affects Google Chrome on Android <151.0.7922.109, Android devices running affected Chrome builds. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-19170?
Update Chrome on Android to 151.0.7922.109 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote sandbox escape via crafted HTML/WebGL, enabling remote code execution on Android Chrome (sandbox bypass).
Immediate action required
- affected< 151.0.7922.109
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.