Affects Google Chrome (widely used). Sandbox escape from renderer can lead to host code execution across organizations; high-impact, must be broadly communicated.
CVE-2026-18002
Chrome Google Lens input flaw allows renderer-to-host sandbox escape.
Is CVE-2026-18002 being exploited?
Not confirmed. CVE-2026-18002 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.21% probability of exploitation in the next 30 days.
How severe is CVE-2026-18002?
CVE-2026-18002 is rated Critical. 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-18002?
Yes. A fix has been recorded for CVE-2026-18002. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-18002 affect?
CVE-2026-18002 affects Google Chrome (Google Lens) versions prior to 151.0.7922.72, Chromium-based browsers with Lens integration. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-18002?
Update Chrome to 151.0.7922.72 or later immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A compromised renderer using crafted HTML can escape the Chrome sandbox and execute code on the host.
Immediate action required
- affected< 151.0.7922.72
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.