EUVD-2026-105673
GHSA-xjrh-3fv4-h5fw
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage drives ANGLE graphics processing
-
ExecutionTrigger use-after-free in freed object
-
ImpactExecute arbitrary code in renderer sandbox
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
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 load attacker-controlled HTML content in an affected Google Chrome build prior to 156.0.8078.47, exercising the ANGLE graphics backend - the default WebGL/graphics translation layer, so no non-default configuration is needed. The key limiting factors are: (1) user interaction (UI:R) - the victim must visit or be redirected to the crafted page; and (2) the resulting code execution is confined to the renderer sandbox, so turning this into host compromise requires an additional sandbox-escape chain. Authentication is not required (PR:N). |
| Impact | Multiple signals align toward genuine priority, with one important nuance. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R) describes network-reachable, low-complexity, unauthenticated exploitation requiring only that a victim visit a page - the classic drive-by profile for a browser renderer bug, and CWE-416 use-after-free is a well-established path to code execution. However, the description explicitly scopes the outcome to 'execute arbitrary code inside the sandbox,' and Chromium itself rated the security severity only Medium, which is in tension with the 8.8/High CVSS; the 8.8 reflects renderer-process impact, not full host compromise, since a working real-world attack would still need to be chained with a separate sandbox-escape to reach the OS. No EPSS score, SSVC decision, KEV listing, or POC indicator is present in the input, so exploitation probability and automatability cannot be quantified - treat the absence as missing data, not as evidence of low risk. Net: patch promptly as a standard high-priority browser update, but recognize that in-isolation this is sandbox-contained code execution rather than a confirmed single-shot full-system RCE. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page (or injects a crafted iframe/ad into a legitimate site) that drives ANGLE into a use-after-free condition when a victim using an unpatched Chrome browser loads it. Successful exploitation yields arbitrary code execution within the renderer sandbox; no public exploit code is identified at time of analysis, and reaching the underlying OS would require chaining an additional sandbox-escape vulnerability. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
A use-after-free in ANGLE, the graphics translation layer behind Chrome's WebGL and hardware-accelerated canvas rendering, lets a crafted HTML page corrupt renderer memory and achieve arbitrary code execution inside the browser sandbox in Google Chrome builds prior to 156.0.8078.47. Exploitation is unauthenticated (PR:N) but requires the victim to load attacker-controlled web content that exercises WebGL paths, and no non-default configuration is needed - the component is enabled by default. Multiple signals align toward genuine priority with one important nuance: code execution is confined to the renderer sandbox, so host compromise would require chaining a separate sandbox escape. At time of analysis, no public exploit code and no confirmed active exploitation (CISA KEV) were identified, though the 8.8 CVSS and RCE-class tagging warrant prompt patching.
RemediationAI
Vendor-released patch: Google Chrome 156.0.8078.47, published in the stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html. Upgrade through Chrome's built-in updater (chrome://settings/help) or your OS package manager, and verify the reported version is 156.0.8078.47 or later; Chromium-based browsers and Electron applications should rebase once their maintainers ship the corresponding ANGLE fix. If the update cannot be rolled out immediately, the highest-value compensating control is to disable WebGL - via the --disable-webgl command-line flag or the equivalent enterprise policy - which removes the reachable ANGLE attack surface at the cost of breaking 3D content, WebGL-based visualization and gaming sites, and some accelerated canvas workloads; a narrower option is to allowlist only trusted sites through policy while restricting general browsing. Enabling strict site isolation and keeping renderer sandboxing intact limits the consequence of a successful renderer compromise to a sandbox escape requirement, but does not prevent the in-sandbox code execution itself, so it is a containment measure rather than a substitute for the patch. Because exploitation requires the user to load crafted HTML, blocking untrusted or unclassified web content and mail-borne HTML links for high-risk users reduces exposure during the patch window.
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 open-source translation layer Chromium uses to map OpenGL ES and WebGL calls onto the host's native graphics APIs - Direct3D on Windows, Metal on macOS, and OpenGL/Vulkan on Linux. Because it sits directly beneath WebGL and accelerated 2D canvas, it is reachable by any web page that creates a graphics context, and it processes a large volume of attacker-influenced state (shader source, buffer bindings, texture handles) through a command-buffer/translation pipeline. The assigned CWE-416 (Use After Free) points to a lifetime-management defect: a graphics resource - for example a context, texture, framebuffer, or shader object - can be freed while still referenced by another part of the translation or command-buffer path, leaving a dangling pointer that a crafted sequence of WebGL operations can reclaim and control. Successful heap grooming converts that stale reference into controlled memory corruption and, per the Chromium severity guidance, arbitrary code execution within the renderer process. The Chromium project rated the issue Medium, reflecting the sandbox confinement and required user interaction, whereas the CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) scores the resulting in-sandbox compromise at 8.8.
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 needs only a victim visit (AV:N/AC:L/PR:N/UI:R); renderer-scoped code execution gives high C/I/A with S:U since impact stays within the sandboxed process.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in ANGLE in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome deployments prior to 156.0.8078.47 are exposed to a high-severity use-after-free in the default-enabled ANGLE/WebGL rendering path, allowing crafted web content to run code inside the browser's renderer sandbox. This creates broad browsing risk for employees, but full host compromise would require a separate sandbox escape, and no public exploit identified at time of analysis has been reported. Leadership should prioritize rapid browser patching because Chrome is widely deployed and the vulnerability is unauthenticated and reachable through normal web use.
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
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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