Severity by source
Sources disagree (Medium–Critical)AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
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: google
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds write in ANGLE in Google Chrome on Mac prior to 149.0.7827.53 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: Medium)
AnalysisAI
Sandbox escape in Google Chrome on macOS prior to 149.0.7827.53 allows a remote attacker who has already compromised the renderer process to break out of the browser sandbox via an out-of-bounds write in ANGLE triggered by a crafted HTML page. The flaw carries a high CVSS of 9.6 due to scope change and full CIA impact, though no public exploit has been identified and EPSS exploitation probability remains very low at 0.03%.
Technical ContextAI
ANGLE (Almost Native Graphics Layer Engine) is Chromium's cross-platform graphics abstraction layer that translates OpenGL ES API calls into the host platform's native graphics API - on macOS this means translation to Metal or OpenGL. The root cause is CWE-787 (Out-of-bounds Write), a memory-corruption class where code writes past the bounds of an allocated buffer, typically due to missing or incorrect length validation in parsing or rendering paths. Because ANGLE runs in the GPU process (a more privileged context than the renderer sandbox), a memory-corruption bug there is a classic stepping stone from a renderer-process compromise to a sandbox escape on macOS specifically.
RemediationAI
Vendor-released patch: Chrome 149.0.7827.53 for macOS - update Chrome via Help > About Google Chrome or rely on the auto-update channel, and confirm via the Chrome Releases advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html. In managed Mac fleets, push the updated build through MDM (Jamf, Intune, Kandji) and verify version compliance. No vendor workaround is documented; as a compensating control until patching, you can reduce the attack surface of the chained renderer-bug-plus-sandbox-escape by disabling hardware acceleration in chrome://settings (which forces software rendering and bypasses much of ANGLE's GPU-process code), with the trade-off of degraded performance for video, WebGL, and Canvas-heavy sites.
Same weakness CWE-787 – Out-of-bounds Write
View allSame technique Buffer Overflow
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 |
Share
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-34492
GHSA-gvr2-h97m-hwr5