Chrome is ubiquitously deployed; this flaw allows arbitrary code execution outside the sandbox on endpoints, risking widespread endpoint compromise.
CVE-2026-76018
Privilege escalation in Google Chrome allowing code execution outside the sandbox via crafted file.
Is CVE-2026-76018 being exploited?
Not confirmed. CVE-2026-76018 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.39% probability of exploitation in the next 30 days.
How severe is CVE-2026-76018?
CVE-2026-76018 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-76018?
Yes. A fix has been recorded for CVE-2026-76018. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76018 affect?
CVE-2026-76018 affects Google Chrome prior to 151.0.7922.173, Chrome Desktop (Windows/macOS/Linux). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76018?
Update Chrome to 151.0.7922.173 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker using social engineering can execute arbitrary code outside Chrome's sandbox, leading to full user/endpoint compromise.
Patch when possible
- affected< 151.0.7922.173
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.