EUVD-2026-105438
GHSA-mm95-6w9g-chvc
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious web page
-
ExploitServe crafted HTML/WebGL content
-
ExecutionTrigger ANGLE memory corruption
-
ImpactExecute arbitrary code in 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 use the WebGL/graphics rendering path in Chrome (ANGLE) and to open attacker-controlled HTML content - the vector is purely web-driven against affected Chrome builds prior to 156.0.8078.47, with no authentication needed (PR:N). The key LIMITING factors are: (1) mandatory user interaction (UI:R) - the victim must navigate to or load the crafted page; and (2) the resulting code execution is confined to the renderer sandbox (scope unchanged), so full host compromise additionally requires a separate sandbox-escape vulnerability. No special non-default configuration is required, as WebGL/ANGLE is enabled by default. |
| Impact | This is a genuine high-priority patch item but not a drop-everything emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) indicates a network-reachable, low-complexity, unauthenticated flaw that requires only that a victim open a crafted HTML page - trivially achievable via a malicious or compromised website. The CWE-119 memory-corruption bug in ANGLE (Chrome's OpenGL ES abstraction layer, reachable from WebGL) is exactly the class Chrome attackers chain. However, the description explicitly scopes the outcome to 'execute arbitrary code inside the sandbox,' which is consistent with S:U (scope unchanged) - meaning this alone yields code execution confined to the renderer sandbox and would need to be chained with a separate sandbox-escape to achieve full host compromise. This materially lowers standalone real-world impact versus a full RCE. No EPSS score was provided in the input, the CVE is NOT in CISA KEV, and no public exploit (POC) is indicated, so there is currently no evidence of active exploitation - the signals do not conflict, they are simply absent. Treat as a standard Chrome 'High' severity update: deploy on normal expedited browser-patch timelines given Chrome's ubiquity and the ease of delivery. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted WebGL/HTML content that triggers the ANGLE memory-corruption bug when a victim running a vulnerable Chrome build visits it. Successful exploitation yields arbitrary code execution within the renderer sandbox; the attacker would then need a separate sandbox-escape to affect the host. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Memory corruption in ANGLE, Chrome's WebGL/graphics translation layer, lets remote attackers potentially achieve arbitrary code execution inside the renderer sandbox on Chrome builds prior to 156.0.8078.47 by convincing a victim to load a crafted HTML page. The bug is rated CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-119), with the mandatory user-interaction requirement and unchanged sandbox scope being the main constraints - full host compromise would require chaining a separate sandbox-escape flaw. Google has released a fixed build, and no public exploit code or confirmed active exploitation (CISA KEV) was identified at time of analysis, making this a high-priority patch item rather than a drop-everything emergency.
RemediationAI
Vendor-released patch: Google Chrome 156.0.8078.47 (stable channel update for desktop, https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html). Update through the browser's built-in updater and confirm the version at chrome://version; enterprise fleets should push the build via their update tooling (e.g. Google Update policies, Chrome Browser Cloud Management, or package managers such as MSI/DEB/RPM) and verify compliance. If immediate rollout is not possible, the most direct compensating control is to disable WebGL rendering - via the --disable-webgl command-line flag or the WebGLBlocklists/DisabledSchemes-style enterprise policy - accepting that this breaks 3D web applications, maps, and some CAD/visualization tooling for users. Enabling strict site isolation (default on desktop) and restricting navigation to trusted sites reduces exposure to the crafted-HTML delivery vector at the cost of some usability. Because code execution is confined to the renderer sandbox, ensuring the browser process remains sandboxed and keeping the rest of the platform patched limits the impact of any successful exploitation pending the update.
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
ANGLE (Almost Native Graphics Layer Engine) is the cross-platform graphics abstraction library Chrome uses to implement WebGL and hardware-accelerated 2D canvas rendering, translating OpenGL ES calls into Direct3D, Metal, Vulkan, or native OpenGL. The flaw is classified as CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer), i.e. an out-of-bounds read/write class defect in ANGLE's handling of attacker-influenced graphics data driven from a web page. Because WebGL/ANGLE is enabled by default with no special configuration, any user browsing to hostile HTML content exercises the vulnerable parsing and rendering path; successful corruption yields code execution with renderer-process privileges. The CVSS scope is unchanged (S:U), so the impact is bounded by Chrome's renderer sandbox - escaping to the host requires a second, independent vulnerability. The associated Chromium issue (issues.chromium.org/issues/556750158) and the Chrome stable channel release notes carry the technical detail.
Know when Chrome gets its next vulnerability
- 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:H/A:H
Remote crafted page with no auth gives AV:N/AC:L/PR:N, but victim must open the page (UI:R); code stays within the renderer sandbox so S:U with full C/I/A inside that boundary.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Memory corruption in ANGLE in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
Executive ViewAI
Google Chrome builds prior to 156.0.8078.47 contain a memory corruption flaw in the ANGLE graphics layer that can be triggered by any employee who simply visits a crafted web page, exposing the browser renderer to potential code execution. Because Chrome is deployed broadly across the workforce and the only prerequisite is user browsing, leadership should treat this as a high-priority fleet-wide patch item with a defined remediation deadline rather than an emergency, since no public exploit code or active exploitation has been identified.
Apply vendor patch.
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.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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
Exploit-DB