Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in ANGLE in Google Chrome prior to 148.0.7778.216 allowed a remote attacker to potentially perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Out-of-bounds read in Google Chrome's ANGLE graphics abstraction layer (versions prior to 148.0.7778.216) allows remote unauthenticated attackers to potentially read limited memory contents from within the browser's process space when a user visits a crafted HTML page. The flaw originates from an inappropriate implementation within ANGLE's rendering pipeline - Chrome's cross-platform graphics engine - resulting in a CWE-125 out-of-bounds read condition with limited confidentiality impact (C:L) and no integrity or availability consequences. No public exploit code has been identified at time of analysis, and EPSS scores this at 0.03% (11th percentile), indicating very low real-world exploitation probability.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is an open-source graphics abstraction library embedded in Google Chrome that translates OpenGL ES API calls to platform-native graphics backends - Direct3D on Windows, Metal on macOS, and Vulkan where available. This design allows Chrome to deliver consistent WebGL and GPU-accelerated rendering across operating systems. The vulnerability (CWE-125: Out-of-Bounds Read) arises from an inappropriate implementation within ANGLE's rendering logic, where insufficient bounds validation permits memory reads beyond an allocated buffer boundary. The CVSS vector's unchanged scope (S:U) constrains the read to Chrome's own process memory rather than the broader OS. Despite being tagged 'Buffer Overflow,' the CWE-125 classification and C:L/I:N/A:N impact profile confirm this is a read-only overread rather than a write-based overflow. Affected product per CPE: cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, covering all Chrome desktop versions prior to 148.0.7778.216.
RemediationAI
The primary fix is to update Google Chrome to version 148.0.7778.216 or later, which contains the vendor-released patch resolving this ANGLE out-of-bounds read. The stable channel update is detailed at http://chromereleases.googleblog.com/2026/05/stable-channel-update-for-desktop_0877304591.html. Enterprise deployments should leverage Chrome's managed update and ExtensionInstallForcelist policies to accelerate rollout across endpoints. For environments where immediate patching is not operationally feasible, enforcing web content filtering and restricting user navigation to only allowlisted or trusted domains reduces exposure by limiting the likelihood of a victim visiting a crafted HTML page - note this restricts general browsing and may affect business workflows. No workarounds that disable ANGLE specifically without breaking Chrome's rendering functionality have been identified from available data.
Same weakness CWE-125 – Out-of-bounds Read
View allSame technique Buffer Overflow
View allVendor StatusVendor
SUSE
Severity: Medium| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-33208
GHSA-pprh-65v6-vjr8