EUVD-2026-105447
GHSA-gp73-fffp-qjwc
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted HTML page
-
ExploitPage triggers ANGLE graphics processing
-
ExecutionExploit 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 | Requires the victim to actively visit or be redirected to an attacker-crafted HTML page that exercises Chrome's ANGLE graphics backend (WebGL/GPU rendering path) on Windows - user interaction (UI:R) is mandatory, so this is not a zero-click flaw. Exploitation affects Chrome versions prior to 156.0.8078.47 on Windows only. The decisive limiting factor is that resulting code execution is confined to the renderer sandbox (S:U, 'inside the sandbox'); escaping to the host requires a separate, unlisted sandbox-escape vulnerability. No authentication is required (PR:N), and default Chrome configurations are affected since ANGLE is the standard graphics layer. |
| Impact | Signals align on moderately-high but not emergency priority. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 8.8) indicates a remote, unauthenticated, low-complexity flaw requiring only that a victim open a crafted HTML page - consistent with a drive-by browser bug. However, the description is explicit and critical: code execution is achieved 'inside the sandbox,' meaning this is a renderer-process compromise, NOT a full host takeover. Absent a chained sandbox-escape, real-world impact is contained to the renderer, which materially lowers practical severity below what the 8.8 score alone implies. No EPSS score was provided in the input, so exploitation probability cannot be quantified. This CVE is NOT in CISA KEV and no public POC or exploit code is referenced - exploitation status is therefore 'no public exploit identified at time of analysis.' The scope is marked unchanged (S:U), which is consistent with sandbox containment. Net assessment: a legitimate must-patch browser vulnerability (Chromium-rated High) that should be remediated promptly via the stable-channel update, but the sandbox-contained nature means it is not independently a critical RCE unless combined with a separate escape. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing malicious WebGL/graphics content that triggers the use-after-free in Chrome's ANGLE component, then lures a Windows user into visiting it. When the page is rendered, the freed memory is reused to gain arbitrary code execution within the Chrome renderer sandbox. No public exploit code is referenced at time of analysis; weaponization would additionally require a sandbox escape to affect the host. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Use-after-free in ANGLE, Chrome's WebGL/graphics translation layer, allows remote attackers to execute arbitrary code inside the renderer sandbox on Windows by luring a victim into opening a crafted HTML page. Exploitation requires user interaction (UI:R) - a page that drives the WebGL/GPU rendering path - and affects Chrome builds on Windows earlier than 156.0.8078.47; unauthenticated remote delivery is possible (PR:N) and default installations are exposed because ANGLE is the standard graphics backend. Code execution is confined to the renderer sandbox (S:U), so full host compromise would require chaining a separate sandbox-escape flaw; no public exploit code or confirmed active exploitation was identified at time of analysis, and Google rates the issue High severity with a vendor patch available.
RemediationAI
Vendor-released patch: upgrade Google Chrome for Windows to 156.0.8078.47 or later - the fix ships in the Stable channel update documented at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html (tracking issue https://issues.chromium.org/issues/563354824). Most users receive it automatically via Chrome's built-in updater; verify with chrome://version and, in managed fleets, force the update through Google Update/Chrome policies and confirm the reported version rather than assuming the auto-updater ran. If the upgrade cannot be staged immediately, the most direct compensating control is to disable WebGL and hardware acceleration (enterprise policy or the --disable-webgl / --disable-gpu launch flags), which removes the reachable attack surface - at the cost of breaking WebGL applications, browser-based 3D/CAD tools, and some mapping and video experiences, so scope it to high-risk user groups and revert once patched. Reducing exposure to untrusted HTML (blocking uncategorized sites, tightening Safe Browsing and content filtering) lowers deliverability but is not a substitute for the patch, and note that update-driven restarts are required for the fix to take effect in already-running browser sessions.
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 translation layer Chrome uses to map OpenGL ES and WebGL calls onto the platform's native graphics API - Direct3D on Windows - making it the mandatory path for any WebGL content rendered in the browser. The flaw is a CWE-416 use-after-free: a graphics object (surface, buffer, or shader resource) is released while a reference to it is still held in the translation/command-submission path, so the freed allocation can be reclaimed with attacker-influenced data and later dereferenced. Because WebGL is reachable directly from JavaScript on an attacker-controlled page, a remote attacker can shape heap layout and trigger the stale reference deterministically enough to redirect execution. The result is arbitrary code execution at renderer/GPU-process privilege inside Chrome's sandbox (S:U), meaning an attacker gets code execution but not direct host access - escaping the sandbox is a distinct, unlisted prerequisite. Only Windows builds prior to 156.0.8078.47 are described as affected; authentication is not required (PR:N) and the only gate is the victim loading the crafted page (UI:R).
Know when Windows 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 privileges but mandatory user interaction (UI:R); unchanged scope reflects sandbox containment, with high C/I/A within the compromised renderer.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in ANGLE in Google Chrome on on Windows 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: High)
Executive ViewAI
Google Chrome on Windows endpoints prior to build 156.0.8078.47 carries a high-severity memory corruption flaw in ANGLE, the graphics layer used by default for WebGL rendering, meaning ordinary browsing activity is sufficient to reach the vulnerable code. An attacker who convinces an employee to open a crafted web page could run code inside the browser's renderer process; because that code is contained by the renderer sandbox, full workstation takeover would require a second, independent exploit. Leadership should care because Chrome is deployed broadly across the Windows fleet, the barrier to delivery is a single malicious link, and remediation is a routine browser update that closes the exposure before attackers have an incentive to build exploit tooling.
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.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
Command injection in the Windows Shell lets remote, unauthenticated attackers bypass a Windows security feature and then
External control of file name or path in Windows NTLM allows an unauthorized attacker to perform spoofing over a network
Exploit-DB