Chrome is a widely used enterprise browser; an RCE in V8 can lead to large-scale user compromise and is notable for all IT teams.
CVE-2026-110169
Use-after-free in V8 allows remote code execution in Chrome sandbox (pre-155.0.8059.79).
Is CVE-2026-110169 being exploited?
Not confirmed. CVE-2026-110169 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-110169?
CVE-2026-110169 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-110169?
Yes. A fix has been recorded for CVE-2026-110169. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-110169 affect?
CVE-2026-110169 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-110169?
Update 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.
Remote code execution via crafted HTML in Chrome's V8 engine; attacker can run arbitrary code in renderer sandbox and potentially compromise browsers.
Immediate action required