Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker crafts malicious HTML/WebGL page
-
DeliveryVictim clicks phishing link or visits compromised site
-
ExploitChrome ANGLE layer processes crafted graphics payload
-
ExecutionUninitialized resource allocated without memory zeroing
-
PersistOut-of-sandbox memory contents read into renderer
-
ImpactSensitive memory data exfiltrated to attacker
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Variable initialization
|
| Exploitation Conditions | Exploitation requires a user running Google Chrome prior to version 152.0.7977.65 to visit an attacker-controlled or attacker-influenced HTML page - user interaction is mandatory (confirmed by UI:R in the CVSS vector). The attack is network-accessible and requires no authentication (PR:N), meaning no credentials or session tokens are needed, but the victim must actively navigate to the malicious content. The vulnerability is triggered through normal graphics rendering via the ANGLE subsystem; no special Chrome configuration, non-default flags, or specific extensions are required beyond a standard Chrome installation. Exploitation is meaningfully limited by: (1) the user-interaction requirement preventing passive or drive-by exploitation without some social engineering vector; (2) the read-only impact - no code execution or integrity modification, limiting the flaw to information disclosure without a chained exploit; and (3) the availability of an automatic vendor patch that most up-to-date Chrome deployments will have already received. |
| Impact | The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N characterizes this as a remotely triggerable, low-complexity information disclosure requiring only that a user visit a crafted page. Despite the High confidentiality impact rating, EPSS stands at just 0.29% (21st percentile), indicating that exploitation has not been widely observed and no weaponized code is circulating at this time. The vulnerability is absent from CISA KEV, and no POC has been identified from available data. The Unchanged scope (S:U) is notable: while memory outside the sandbox is readable, this does not constitute a full sandbox escape - lateral movement or code execution would require chaining with additional exploits. The gap between the High CVSS confidentiality score and the low EPSS percentile suggests this flaw is theoretically impactful but practically difficult to exploit reliably without additional primitives. The user-interaction requirement (UI:R) further limits opportunistic mass exploitation, constraining realistic risk to targeted or phishing-assisted scenarios. Patch availability from Google substantially reduces residual risk for organizations with timely update posture. |
| Exploit ScenarioDerived | An attacker hosts a malicious HTML page containing crafted WebGL or graphics-intensive content designed to trigger an uninitialized resource allocation within Chrome's ANGLE layer. When a victim with a vulnerable Chrome version navigates to the page - for example, via a phishing link or a compromised advertisement - the browser processes the graphics payload, reads uninitialized memory from outside the renderer sandbox, and potentially exposes sensitive process memory contents to the attacker via a side channel or direct data exfiltration path. No public exploit or POC code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 28, 2026
Memory disclosure in Google Chrome's ANGLE graphics subsystem (prior to 152.0.7977.65) exposes out-of-sandbox memory contents when a user visits a crafted HTML page. The uninitialized resource flaw (CWE-908) in ANGLE - Chrome's cross-platform graphics abstraction layer - allows a remote attacker to read memory that should be isolated within the renderer sandbox, leading to high-confidence confidentiality impact. No public exploit has been identified at time of analysis, and EPSS at 0.29% reflects currently low exploitation probability despite the high CVSS confidentiality rating.
RemediationAI
Upgrade Google Chrome to version 152.0.7977.65 or later, which contains the vendor-released patch per the stable channel advisory at https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. Chrome's built-in auto-update mechanism will apply this fix automatically for most consumer installations; enterprise administrators should verify deployment status via Chrome Browser Cloud Management or group policy. Where immediate updates are not feasible, restricting user access to untrusted or external web content through a proxy or content-filtering solution reduces exposure, though this carries significant productivity trade-offs in a general-purpose browser environment. Disabling GPU-accelerated rendering via the --disable-gpu flag is a more targeted compensating control that would limit ANGLE attack surface, but it degrades browser performance and may break rendering on media-heavy sites.
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 Chromium's graphics abstraction layer that translates OpenGL ES API calls into platform-native graphics APIs such as DirectX (Windows), Metal (macOS), and Vulkan. CWE-908 (Use of Uninitialized Resource) indicates that a graphics resource - likely a buffer, texture, or shader input - is allocated without being zeroed or fully initialized before being read. Because ANGLE operates at the boundary between the sandboxed renderer process and the underlying OS graphics stack, an uninitialized allocation in this component can expose memory from outside the renderer's isolated address space. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome versions prior to 152.0.7977.65.
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
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Network-delivered via crafted webpage with no auth required (PR:N), but user must actively visit the page (UI:R); impact is confidentiality-only due to read-outside-sandbox memory disclosure with no write or availability effect.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
3DescriptionCVE.org
Uninitialized resource in ANGLE in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Threat Intelligence Overview
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Same weakness CWE-908 – Use of Uninitialized Resource
View allSame technique Information Disclosure
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-65895
GHSA-9f9f-2jqj-rq6g
NVD
CVE.org
EPSS
Exploit-DB