Chrome is widely deployed across enterprises; an RCE that escapes the browser sandbox can lead to endpoint compromise and lateral movement, requiring org-wide mitigation.
CVE-2026-110138
Chrome use-after-free in ShapeDetection enables remote code execution outside the sandbox
Is CVE-2026-110138 being exploited?
Not confirmed. CVE-2026-110138 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.30% probability of exploitation in the next 30 days.
How severe is CVE-2026-110138?
CVE-2026-110138 is rated High with a CVSS score of 8.3. 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-110138?
Yes. A fix has been recorded for CVE-2026-110138. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-110138 affect?
CVE-2026-110138 affects Google Chrome (desktop) versions 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-110138?
Update Chrome to 155.0.8059.79 or later immediately via enterprise patch management.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution outside Chrome sandbox via crafted HTML after renderer process compromise (escape sandbox, run arbitrary code).
Immediate action required