Google Chrome EUVD-2026-34709

The target must be running Chrome desktop prior to 149.0.7827.53 with the Google Lens feature enabled (default in Stable Channel). The attacker must deliver a specifically crafted HTML page to the victim and the victim must interact with it (CVSS UI:R) in a way that triggers the Lens navigation path - interaction is required, but no authentication on the attacker's side and no privileges on the victim's machine are needed (PR:N). Limiting factors: enterprises that have disabled Lens via policy are not reachable; the bug is scoped to navigation-restriction bypass rather than arbitrary code execution per Google's Low Chromium severity rating, so chained impact depends on what destination the bypass reaches.

Signals here are notably conflicting: the NVD CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) scores 8.8 and projects full CIA impact, but Google's own Chromium rating is 'Low,' which is a strong vendor signal that real-world impact is constrained to a navigation-control bypass rather than RCE or sandbox escape. No EPSS score was provided in the input, the CVE is not in CISA KEV, and no public exploit is identified at time of analysis, so there is no evidence of active exploitation. The require-user-interaction flag (UI:R) further limits opportunistic attacks. Practical priority: patch on a normal Chrome update cadence; the headline 8.8 overstates urgency given the vendor's Low severity and the absence of exploitation indicators. Note: the CVSS C:H/I:H/A:H rating appears inconsistent with a 'navigation restriction bypass' and Chromium's Low severity - defenders should treat the precise impact as uncertain until the Chromium issue tracker entry (497946941) is public.

An attacker hosts a crafted HTML page and lures a Chrome user (pre-149.0.7827.53) to visit it, for example through phishing or a malvertising redirect. When the user interacts with the page in a way that engages Google Lens (such as a right-click 'Search image with Google Lens' or an embedded Lens-triggering element), the malformed content causes Lens to navigate outside its intended restriction boundary, sending the browser to a URL or origin that should have been blocked. No public proof-of-concept has been identified at time of analysis.