Remote code execution in widely used Google Chrome; affects many endpoints and merits broad IT notification.
CVE-2026-91715
Type confusion in Chrome ServiceWorker allows sandboxed remote code execution.
Is CVE-2026-91715 being exploited?
Not confirmed. CVE-2026-91715 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-91715?
CVE-2026-91715 is rated High with a CVSS score of 8.8. 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-91715?
Yes. A fix has been recorded for CVE-2026-91715. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91715 affect?
CVE-2026-91715 affects Google Chrome (Desktop) prior to 153.0.8010.47 on Windows/macOS/Linux. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-91715?
Update Chrome to 153.0.8010.47 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can execute arbitrary code in the browser sandbox via a crafted HTML/ServiceWorker page, enabling compromise of user endpoints and data.
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.