High-severity remote code execution in Google Chrome — a ubiquitous browser used across all industries; requires org-wide remediation and will attract broad attention.
CVE-2026-76031
Use-after-free in Chrome Input enables sandboxed remote code execution.
Is CVE-2026-76031 being exploited?
Not confirmed. CVE-2026-76031 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-76031?
CVE-2026-76031 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-76031?
Yes. A fix has been recorded for CVE-2026-76031. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-76031 affect?
CVE-2026-76031 affects Google Chrome (desktop) versions 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-76031?
Update Chrome to 156.0.8078.79 or later immediately.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Crafted HTML can trigger a use-after-free in Chrome's renderer allowing arbitrary code execution inside the browser sandbox.
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.