Chrome is widely deployed; a sandbox escape allowing arbitrary code execution can lead to widespread system compromise and enterprise disruption.
CVE-2026-110159
Local code execution outside Chrome sandbox via Updater (<=155.0.8059.79).
Is CVE-2026-110159 being exploited?
Not confirmed. CVE-2026-110159 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-110159?
CVE-2026-110159 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-110159?
Yes. A fix has been recorded for CVE-2026-110159. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-110159 affect?
CVE-2026-110159 affects Google Chrome (prior to 155.0.8059.79). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-110159?
Upgrade Chrome to 155.0.8059.79 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can execute arbitrary code outside Chrome sandbox, enabling privilege escalation and full system compromise.
Immediate action required