EUVD-2026-54136
GHSA-q7v3-32hw-67w6
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
AC:H reflects mandatory renderer pre-compromise; C:L for cross-origin read only; no integrity or availability impact observed.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Integer overflow in GPU in Google Chrome prior to 151.0.7922.109 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Cross-origin data leakage in Google Chrome's GPU process - caused by an integer overflow (CWE-190) - enables a remote attacker who has already achieved renderer process compromise to read data across origin boundaries by delivering a crafted HTML page. All Chrome desktop releases prior to 151.0.7922.109 are affected. No public exploit or CISA KEV listing exists at time of analysis; the chained nature of the attack (requiring a prior renderer compromise) substantially constrains real-world risk despite the broad deployment footprint of Chrome.
Technical ContextAI
Google Chrome's multi-process architecture isolates web content in sandboxed renderer processes, which communicate with a separate GPU process responsible for compositing and hardware-accelerated graphics. CWE-190 (Integer Overflow or Wraparound) in the GPU process indicates that a numeric calculation - likely involving buffer sizes, offsets, or texture dimensions - wraps around its integer type boundary, producing an unexpectedly small value. This miscalculation can cause the GPU process to read from or expose memory regions outside the intended allocation, potentially containing data from cross-origin contexts that were previously rendered. Because the GPU process receives commands from the (already-compromised) renderer, the attacker controls the crafted inputs that trigger the overflow. The EUVD-affected version string 'Chrome 151.0.7922.109 <151.0.7922.109' confirms all stable channel builds prior to the patch release are in scope.
RemediationAI
Vendor-released patch: Chrome 151.0.7922.109. Users and administrators should update all Chrome desktop installations to version 151.0.7922.109 or later immediately, using Chrome's built-in update mechanism (chrome://settings/help) or via enterprise deployment tooling (Google Admin Console, MSI/MSP packages). The official stable channel release advisory is at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_01193673229.html. Because exploitation requires a prior renderer process compromise, organizations that cannot immediately patch can partially reduce risk by enforcing Chrome's Site Isolation feature (already enabled by default in modern Chrome) and restricting user access to untrusted or high-risk web destinations via proxy policy - though these are compensating controls only and do not address the vulnerability. No workaround eliminates the integer overflow itself.
Same weakness CWE-190 – Integer Overflow or Wraparound
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today