Chrome is widely used across enterprises; an RCE that escapes the sandbox on Android affects many users and warrants broad IT notification.
CVE-2026-95322
OOB write in Chrome GPU on Android allows sandbox escape and remote code execution.
Is CVE-2026-95322 being exploited?
Not confirmed. CVE-2026-95322 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.
How severe is CVE-2026-95322?
CVE-2026-95322 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-95322?
Yes. A fix has been recorded for CVE-2026-95322. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-95322 affect?
CVE-2026-95322 affects Google Chrome for Android <154.0.8037.57. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-95322?
Upgrade Chrome for Android to 154.0.8037.57+ and advise users to avoid untrusted webpages.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted HTML exploiting GPU out-of-bounds write, enabling renderer compromise, sandbox escape and arbitrary code execution on Android devices.
Immediate action required
- affected< 154.0.8037.57
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.