Chrome is a widely deployed enterprise product; a sandbox escape enabling arbitrary code execution outside the browser is high-impact and warrants broad IT notice.
CVE-2026-91735
Chrome WebUI auth flaw allows sandbox escape and arbitrary code execution (pre-153.0.8010.47)
Is CVE-2026-91735 being exploited?
Not confirmed. CVE-2026-91735 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-91735?
CVE-2026-91735 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-91735?
Yes. A fix has been recorded for CVE-2026-91735. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91735 affect?
CVE-2026-91735 affects Google Chrome (Desktop) < 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-91735?
Update Chrome to 153.0.8010.47 or later immediately; limit access to untrusted content until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape: attacker with a compromised renderer can execute arbitrary code outside Chrome's sandbox via crafted HTML.
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.