EUVD-2026-105674
GHSA-qmwm-8h6v-vg78
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to crafted web page
-
ExploitChrome renders malicious content in ANGLE
-
ExecutionTrigger memory corruption in graphics layer
-
ImpactRead sensitive process memory
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 a user running Google Chrome prior to 156.0.8078.47 to load an attacker-controlled or attacker-injected HTML page that exercises the vulnerable ANGLE code path; this is reflected by UI:R in the CVSS vector, so some user interaction (visiting/rendering the page) is the primary limiting factor. No authentication is required (PR:N) and no special non-default configuration is indicated - ANGLE is Chrome's default graphics translation layer, so default desktop installs are affected. The description does not state the specific rendering operation or content that triggers the memory corruption, so the exact trigger is not described in the available sources. Limiting factors beyond user interaction: the victim must be on an unpatched build, and the disclosed impact per the description is reading memory rather than confirmed code execution. |
| Impact | Signals conflict and should be reconciled before prioritizing. NVD scores this 8.8 (High) with vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, yet the Chromium project rated it Medium, and the description states only that an attacker can 'read memory' - i.e. information disclosure/confidentiality - which does not obviously support the C:H/I:H/A:H (full integrity and availability) impact in the NVD vector; this mismatch should be verified with the vendor. Exploitation signals are low: EPSS is 0.22% (11th percentile), the CVE is not in CISA KEV, and no public exploit was identified in the provided data (the chromium issue tracker link is a restricted bug reference, not working exploit code). The vuln.today decision label is 'this_week', consistent with a patched browser flaw requiring user interaction (UI:R) rather than an emergency. Net: this is a patch-on-the-normal-browser-update-cadence issue - a genuine memory-safety bug in a near-ubiquitous product, but current exploitation probability is low and no in-the-wild activity is confirmed. The main caveat is the severity/impact disagreement (NVD High + C/I/A:H vs Chromium Medium + read-only description). |
| Exploit ScenarioDerived | An attacker hosts or injects a crafted HTML page that drives Chrome's ANGLE graphics component into a memory-corruption condition when the page is rendered. A victim running a vulnerable Chrome build (prior to 156.0.8078.47) simply visits the page, and the flaw lets the attacker read process memory, potentially leaking sensitive in-browser data. 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 22, 2026
Memory corruption in ANGLE, the graphics translation layer built into Google Chrome, allows a remote attacker to read memory from the browser process when a victim renders a crafted HTML page on any build prior to 156.0.8078.47. Exploitation needs user interaction (the victim must load the page) but no credentials, and the disclosed impact is a confidentiality breach via memory disclosure rather than confirmed code execution, so the independent assessment scores it AV:N/AC:L/PR:N/UI:R/C:H/I:N/A:N rather than the vendor-supplied 8.8 with full integrity and availability impact. Chrome's own severity rating is Medium, EPSS is 0.22% (11th percentile), and no public exploit code has been identified at time of analysis; Google has released a fix in the 156.0.8078.47 stable channel update.
RemediationAI
Google has shipped the fix in Chrome 156.0.8078.47, so the complete remediation is to update to that build or later through the browser's built-in updater and relaunch, or by deploying the corresponding enterprise MSI/PKG/DEB/RPM package from the stable channel advisory at https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html; because Chrome applies updates on restart, an outstanding relaunch leaves the host on the vulnerable build. Patch availability is confirmed by the vendor ('Available from vendor'), and the tracked Chromium issue is https://issues.chromium.org/issues/563352451. The supplied references document no workaround and identify no configuration that removes exposure other than updating, since ANGLE is a default-on component used for WebGL and accelerated canvas rendering; disabling hardware acceleration or WebGL may reduce practical exposure but is not a vendor-stated fix, would break GPU-accelerated content, and still leaves the vulnerable code installed. Prioritization is set to this_week rather than emergency: EPSS is 0.22% (11th percentile), there is no CISA KEV listing, and no public exploit code has been identified at time of analysis, while the assessed impact is limited to memory disclosure (C:H, I:N, A:N) contingent on the user rendering the crafted page.
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 graphics abstraction shipped inside Chrome that implements OpenGL ES semantics on top of Direct3D, Metal, Vulkan or desktop OpenGL; web content reaches it through WebGL and hardware-accelerated canvas rendering. The flaw is classified CWE-119 (improper restriction of operations within the bounds of a memory buffer), which in this component means a graphics operation can produce an out-of-bounds memory access reachable from a rendered page, and the disclosure specifically describes the outcome as reading memory. The CPE cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* is fully wildcarded, indicating the affected scope is Chrome itself rather than a separately versioned library, and the EUVD record points at builds below 156.0.8078.47. The available sources do not describe the specific GL/WebGL call sequence, shader or resource that triggers the corruption, so the exact trigger is not described in the available sources; what is confirmed is the affected component (ANGLE), the access vector (rendered HTML), and the disclosed impact (memory read). Because ANGLE is enabled by default on desktop installs, no non-default configuration is required to be exposed.
Know when the next one hits your stack
- 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
Delivered via a crafted web page (AV:N, UI:R) with no auth (PR:N); description states only memory read, so C:H with I:N/A:N, diverging from NVD's C:H/I:H/A:H.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
Memory corruption in ANGLE in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to read memory via a crafted HTML page. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome versions prior to 156.0.8078.47 contain a high-severity memory corruption vulnerability in ANGLE that could allow an attacker to read sensitive browser process memory when a user visits a crafted webpage. This affects all employees using unpatched Chrome, potentially exposing confidential data, though no active exploitation has been observed. Leadership should prioritize patching to mitigate risk.
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.
Exploit-DB