Affects a widely used browser on Android; sandbox escape could lead to device compromise across multiple industries.
CVE-2026-13028
Chrome WebGL UAF on Android may sandbox-escape via crafted HTML.
Is CVE-2026-13028 being exploited?
Not confirmed. CVE-2026-13028 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-13028?
CVE-2026-13028 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-13028?
Yes. A fix has been recorded for CVE-2026-13028. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-13028 affect?
CVE-2026-13028 affects Google Chrome for Android (<149.0.7827.197). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-13028?
Update Chrome for Android to 149.0.7827.197 or newer
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution on Android via WebGL; attacker could escape Chrome sandbox.
Patch when possible
- affected< 149.0.7827.197
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.