Widely used Chrome on Android; sandbox-escape raises device compromise risk across org endpoints.
CVE-2026-11012
Use-after-free in Chrome for Android Serial; sandbox escape via crafted HTML.
Is CVE-2026-11012 being exploited?
Not confirmed. CVE-2026-11012 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.29% probability of exploitation in the next 30 days.
How severe is CVE-2026-11012?
CVE-2026-11012 is rated High with a CVSS score of 8.3. 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-11012?
Yes. A fix has been recorded for CVE-2026-11012. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-11012 affect?
CVE-2026-11012 affects Google Chrome for Android (versions < 149.0.7827.53). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-11012?
Update Chrome for Android to 149.0.7827.53+
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape leading to remote code execution on the device via a compromised renderer.
Immediate action required
- affected< 149.0.7827.53
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.