Widely deployed browser; a GPU use-after-free enabling sandbox escape on Android can lead to remote compromise across many organizations and devices.
CVE-2026-15900
Chrome for Android UAF in GPU allows sandbox escape via crafted HTML.
Is CVE-2026-15900 being exploited?
Not confirmed. CVE-2026-15900 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.40% probability of exploitation in the next 30 days.
How severe is CVE-2026-15900?
CVE-2026-15900 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-15900?
Yes. A fix has been recorded for CVE-2026-15900. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-15900 affect?
CVE-2026-15900 affects Google Chrome for Android <150.0.7871.128. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-15900?
Update Chrome for Android to 150.0.7871.128 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 (GPU use-after-free), potentially enabling arbitrary code execution outside Chrome sandbox.
Immediate action required
- affected< 150.0.7871.128
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.