Chrome is ubiquitous; an RCE in the browser sandbox can enable widespread compromise of endpoints and user data across organizations.
CVE-2026-76026
Chrome Autofill memory corruption allows remote code execution in the browser sandbox.
Is CVE-2026-76026 being exploited?
Not confirmed. CVE-2026-76026 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.20% probability of exploitation in the next 30 days.
How severe is CVE-2026-76026?
CVE-2026-76026 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-76026?
Yes. A fix has been recorded for CVE-2026-76026. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76026 affect?
CVE-2026-76026 affects Google Chrome (desktop) prior to 156.0.8078.79. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-76026?
Update Chrome to 156.0.8078.79 or later immediately and enforce auto-updates.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution in Chrome sandbox via crafted HTML; attackers can run arbitrary code and compromise browser data and sessions.
Immediate action required
- affected< 156.0.8078.79
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.