EUVD-2026-33195
GHSA-mcvq-rh64-88v2
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds write in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome's ANGLE graphics layer prior to version 148.0.7778.216 allows a remote attacker who has already compromised the renderer process to break out of Chrome's sandbox via a crafted HTML page. Rated High severity by Chromium with a CVSS of 8.3, the issue is patched but no public exploit has been identified at time of analysis, and EPSS exploitation probability is low (0.03%, 11th percentile).
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is the abstraction library Chrome uses to translate OpenGL ES API calls into the underlying graphics API of the host platform (Direct3D on Windows, Metal on macOS, Vulkan/OpenGL on Linux). It is invoked from the renderer process whenever WebGL, WebGPU, or canvas-accelerated content is rendered. The root cause is CWE-787 (Out-of-Bounds Write) - a memory corruption primitive in ANGLE's processing of graphics commands. Because ANGLE runs in the GPU process boundary that the renderer can interact with, a controlled out-of-bounds write here gives an already-compromised renderer a route to corrupt memory in a more privileged process, enabling sandbox escape. CPE coverage is broad (cpe:2.3:a:google:chrome:*) reflecting that all Chrome desktop builds prior to the fix are affected.
RemediationAI
Vendor-released patch: Chrome Stable 148.0.7778.216 - upgrade to this version or later via the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html. In managed environments, force update via Chrome Browser Cloud Management or the relevant policy (RelaunchNotification) to ensure users restart and pick up the fix. For Chromium-based browsers, apply the corresponding vendor build that incorporates the upstream ANGLE fix. As an interim compensating control where patching is delayed, disabling hardware acceleration in chrome://settings reduces ANGLE attack surface for many code paths, at the cost of degraded WebGL/WebGPU performance and broken graphics in some sites; alternatively, blocking WebGL via enterprise policy (HardwareAccelerationModeEnabled=false or site-specific WebGL policy) shrinks exposure but breaks legitimate 3D and canvas-accelerated content.
Same weakness CWE-787 – Out-of-bounds Write
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: High| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today