EUVD-2026-30470
GHSA-5pg5-5cwg-mr85
Severity by source
AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N
Lifecycle Timeline
3DescriptionCVE.org
Inappropriate implementation in ANGLE in Google Chrome on Windows prior to 148.0.7778.168 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 on Windows via ANGLE graphics library allows renderer-compromised attackers to steal sensitive data from other origins through specially crafted web pages. Affects Chrome versions prior to 148.0.7778.168 on Windows platforms. EPSS probability of 0.03% (10th percentile) indicates low observed exploitation likelihood, with CISA SSVC confirming no active exploitation and non-automatable attack chain. Vendor patch released in Chrome 148.0.7778.168 stable channel update. Attack requires successful renderer process compromise as prerequisite, combined with user interaction, creating a chained exploitation scenario rather than standalone vulnerability.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is Chrome's graphics layer abstraction that translates OpenGL ES API calls to platform-specific graphics APIs - on Windows, it converts WebGL calls to Direct3D. The vulnerability stems from CWE-284 (Improper Access Control) within ANGLE's Windows implementation, allowing improperly restricted access to cross-origin rendering contexts or memory. When rendering isolated origins in separate processes (site isolation), ANGLE should enforce strict boundaries between rendering contexts. This implementation flaw permits a compromised renderer process to bypass same-origin policy protections at the graphics layer, accessing pixel data or rendering state from other origins' WebGL contexts. The Windows-specific nature suggests the issue lies in Direct3D translation layer rather than core ANGLE logic, potentially involving shared texture handles or improperly isolated graphics device contexts.
RemediationAI
Update Google Chrome to version 148.0.7778.168 or later immediately via built-in auto-update mechanism (chrome://settings/help) or download from official Chrome distribution channels at https://www.google.com/chrome/. Chrome's automatic background update typically deploys patches within 24-48 hours for most users. Vendor advisory available at http://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_12.html with technical details at Chromium issue tracker https://issues.chromium.org/issues/500052361. For enterprise environments unable to deploy immediate updates, implement temporary compensating controls: disable WebGL rendering via Group Policy (chrome://flags/#disable-webgl set to Disabled) or use Chrome Enterprise policy 'WebGLAllowedForUrls' to whitelist only trusted domains requiring WebGL functionality. Note that disabling WebGL will break legitimate web applications using 3D graphics, mapping tools, and data visualization requiring GPU acceleration - assess business impact before deployment. No effective network-layer mitigation exists as the vulnerability operates within browser rendering pipeline after content delivery.
Use-after-free vulnerability in the DisplayObject class in the ActionScript 3 (AS3) implementation in Adobe Flash Player
V8 in Google Chrome prior to 54.0.2840.90 for Linux, and 54.0.2840.85 for Android, and 54.0.2840.87 for Windows and Mac
Type confusion in V8 in Google Chrome prior to 59.0.3071.86 for Linux, Windows, and Mac, and 59.0.3071.92 for Android, a
The Array.prototype.concat implementation in builtins.cc in Google V8, as used in Google Chrome before 49.0.2623.108, do
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Incorrect handling of complex species in V8 in Google Chrome prior to 57.0.2987.98 for Linux, Windows, and Mac and 57.0.
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
An issue was discovered in the Cisco WebEx Extension before 1.0.7 on Google Chrome, the ActiveTouch General Plugin Conta
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Use-after-free vulnerability in the BitmapData class in the ActionScript 3 (AS3) implementation in Adobe Flash Player 13
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today