Chrome is ubiquitous; a sandbox-escaping remote code execution in stable Chrome can lead to widespread compromise and requires org-wide attention.
CVE-2026-91710
RCE in Google Chrome WebAppInstalls (use-after-free) allowing code execution.
Is CVE-2026-91710 being exploited?
Not confirmed. CVE-2026-91710 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-91710?
CVE-2026-91710 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-91710?
Yes. A fix has been recorded for CVE-2026-91710. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91710 affect?
CVE-2026-91710 affects Google Chrome <153.0.8010.47 (Windows/macOS/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-91710?
Update Chrome to 153.0.8010.47 or later immediately; restart browsers.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution outside Chrome sandbox via crafted HTML; attacker can run arbitrary code with user-level privileges.
Immediate action required
- affected< 153.0.8010.47
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.