Sandbox escape in widely used Google Chrome (desktop) enables arbitrary code execution outside the renderer; affects many organizations and warrants broad notification and rapid mitigation.
CVE-2026-106228
Chrome Google Lens sandbox escape enabling arbitrary code execution outside the renderer
Is CVE-2026-106228 being exploited?
Not confirmed. CVE-2026-106228 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-106228?
CVE-2026-106228 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-106228?
Yes. A fix has been recorded for CVE-2026-106228. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-106228 affect?
CVE-2026-106228 affects Google Chrome (desktop) < 155.0.8059.39, Google Lens component in Chrome. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-106228?
Update Chrome to 155.0.8059.39+ immediately; enforce site isolation and restrict untrusted content.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Sandbox escape: attacker with a compromised renderer can execute arbitrary code outside Chrome's sandbox via crafted HTML.
Immediate action required
- affected< 155.0.8059.39
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.