Chrome is a widely used browser; sandbox escape allowing arbitrary code execution on macOS is broadly impactful and newsworthy for IT orgs.
CVE-2026-91712
Chrome (macOS) race condition enables sandbox escape and arbitrary code execution.
Is CVE-2026-91712 being exploited?
Not confirmed. CVE-2026-91712 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.25% probability of exploitation in the next 30 days.
How severe is CVE-2026-91712?
CVE-2026-91712 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-91712?
Yes. A fix has been recorded for CVE-2026-91712. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-91712 affect?
CVE-2026-91712 affects Google Chrome for macOS < 153.0.8010.47, Chromium-based browsers (variants may be affected). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-91712?
Update Chrome on 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.
Sandbox escape: attacker controlling renderer via crafted HTML can execute arbitrary code outside Chrome sandbox on macOS.
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.