Chrome on Android is widely deployed; sandbox escape leading to RCE on endpoints is highly impactful across organizations and merits broad IT distribution.
CVE-2026-16419
Out-of-bounds read/write in ANGLE enabling sandbox escape in Chrome for Android.
Is CVE-2026-16419 being exploited?
Not confirmed. CVE-2026-16419 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-16419?
CVE-2026-16419 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-16419?
Yes. A fix has been recorded for CVE-2026-16419. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-16419 affect?
CVE-2026-16419 affects Google Chrome for Android <150.0.7871.182, ANGLE component used by Chrome on Android. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-16419?
Update Chrome for Android to 150.0.7871.182 or later immediately; limit access to untrusted sites.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can escape Chrome sandbox and achieve remote code execution on Android via a crafted HTML page.
Immediate action required
- affected< 150.0.7871.182
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.