Chrome is widely used across organizations; this is a sandbox escape enabling code execution outside the browser on macOS—high-impact and newsworthy.
CVE-2026-91727
Chrome (macOS) extension sandbox escape allowing code execution outside the sandbox
Is CVE-2026-91727 being exploited?
Not confirmed. CVE-2026-91727 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.09% probability of exploitation in the next 30 days.
How severe is CVE-2026-91727?
CVE-2026-91727 is rated High with a CVSS score of 8.1. 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-91727?
Yes. A fix has been recorded for CVE-2026-91727. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91727 affect?
CVE-2026-91727 affects Google Chrome on macOS < 153.0.8010.47. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-91727?
Update Chrome for macOS to 153.0.8010.47 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local sandbox escape: attacker with a compromised renderer can execute arbitrary code outside Chrome sandbox via a local program.
Patch when possible
- 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.