EUVD-2026-105695
GHSA-9jxm-53hj-j6qm
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage invokes Google Lens code path
-
ExecutionTrigger memory corruption (CWE-119)
-
ImpactRead sensitive memory inside sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to navigate to an attacker-controlled web page containing crafted HTML that exercises the Google Lens feature code path in Chrome - this user interaction (UI:R) is the primary limiting factor, as there is no drive-by auto-trigger without the victim loading the page. No authentication is required (PR:N). The impact is further constrained to memory reads within the renderer sandbox: it does not escape the sandbox, write memory, or affect availability, so leaked data is limited to whatever resides in the affected process. Affects Chrome versions prior to 156.0.8078.47 on desktop; updating to that build or later removes the condition. |
| Impact | This is a genuinely low-priority issue despite a moderate 6.5 CVSS base score. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N) describes a network-reachable, low-complexity, unauthenticated flaw requiring user interaction, with high confidentiality impact but no integrity or availability impact - consistent with an information-disclosure bug rather than code execution. Critically, the impact is bounded: the description states the attacker can only 'potentially read memory inside the sandbox,' so this is NOT a sandbox escape, and Chromium itself rated the security severity 'Low,' which conflicts with the C:H in the supplied CVSS vector (sandbox-confined memory reads rarely warrant C:H - this appears to be an overstated confidentiality metric). The EPSS score of 0.19% (9th percentile) indicates very low predicted exploitation likelihood. There is no CISA KEV listing and no public proof-of-concept referenced, so exploitation status is 'no public exploit identified at time of analysis.' No SSVC decision data was provided. Net assessment: a low real-world risk, routine browser patch; the headline 6.5 overstates practical danger given the sandbox-bounded, read-only, user-interaction-gated nature of the flaw. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing crafted HTML that triggers a memory-corruption condition in Chrome's Google Lens component when a victim navigates to it. Successful exploitation could let the attacker read memory contents within the renderer sandbox, potentially leaking sensitive in-process data, but does not by itself escape the sandbox or execute code. No public exploit code is referenced, and exploitation requires the victim to visit the attacker-controlled page (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in the Google Lens component of Google Chrome on desktop allows a remote attacker to read memory within the renderer sandbox by convincing a victim to load a crafted HTML page. Exploitation requires user interaction (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N per independent assessment) and is confined to memory reads inside the already-sandboxed renderer - there is no sandbox escape, no memory write, and no availability impact, which is why Google rated it Chromium security severity Low and EPSS is only 0.19% (9th percentile). No public exploit code or confirmed active exploitation was identified at time of analysis, and Chrome builds from 156.0.8078.47 onward contain the fix.
RemediationAI
Vendor-released patch: Chrome 156.0.8078.47 (and later). Update desktop Chrome through the stable channel release documented at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html and confirm the version via chrome://version; enterprise fleets should push the build through their update tooling or verify via the Chrome Enterprise release notes, since the underlying bug (https://issues.chromium.org/issues/503665813) is access-restricted and provides no self-service detail. No patch-independent fix is known, so interim risk reduction is limited to shrinking the attack surface: disabling the Google Lens feature via enterprise policy or blocking Lens entry points and untrusted image-heavy content reduces exposure but degrades a user-facing feature and is not a true remediation; enforcing site isolation and keeping the renderer sandbox intact is the control that keeps this a low-severity memory-read primitive rather than a broader compromise, and restricting users to curated, trusted browsing profiles lowers the chance of encountering a crafted page. Given the low Chromium severity rating, the absence of public exploit code, and the EPSS score of 0.19%, remediation can follow the normal Chrome update cadence rather than an emergency response, but the upgrade to 156.0.8078.47 should not be deferred indefinitely.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is classified as CWE-119 (improper restriction of operations within the bounds of a memory buffer), which in Chromium practice typically means an out-of-bounds read in native parsing/processing code that operates on attacker-influenced input. Here the vulnerable surface is the Google Lens feature code path, which processes page content (images and associated markup) rendered from an HTML page; a crafted page can drive that code beyond the intended buffer boundary and cause bytes from adjacent heap memory to be returned or exposed to the attacker-influenced context. Critically, this occurs inside the Chrome renderer sandbox: the technology stack involves Blink's document/image handling plus Lens integration, and the sandbox is precisely what limits the read to memory within the compromised renderer process rather than the browser process or the host OS. The upstream bug (issues.chromium.org/503665813) is tracked by Google with restricted access, consistent with Chromium's practice of withholding exploit-relevant detail until users have updated; the public disclosure in the stable channel release notes is the primary technical record. Reported by chrome-cve-admin@google.com and catalogued as EUVD-2026-105695.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network-reachable crafted page needs victim navigation (UI:R, PR:N); impact is a sandbox-confined, partial memory read so C:L not C:H, with no integrity or availability impact.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Memory corruption in Google Lens in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially read memory inside the sandbox via a crafted HTML page. (Chromium security severity: Low)
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Exploit-DB