Chrome is ubiquitous; an RCE in V8 can enable drive-by compromises across organizations and should reach all IT security teams.
CVE-2026-110921
Use-after-free in V8 allows sandboxed RCE in Chrome <155.0.8059.84
Is CVE-2026-110921 being exploited?
Not confirmed. CVE-2026-110921 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.22% probability of exploitation in the next 30 days.
How severe is CVE-2026-110921?
CVE-2026-110921 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-110921?
Yes. A fix has been recorded for CVE-2026-110921. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-110921 affect?
CVE-2026-110921 affects Google Chrome < 155.0.8059.84 (desktop), Chromium-based browsers using same V8 build. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-110921?
Update Chrome to 155.0.8059.84+ 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 renderer via crafted HTML, enabling attacker code execution inside the browser sandbox.
Immediate action required
- affected< 155.0.8059.84
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.