EUVD-2026-50801
GHSA-ww22-288f-wm8m
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
AC:H because reaching ANGLE requires a pre-existing renderer compromise plus a crafted page (UI:R); S:C and C/I/A:H reflect the sandbox escape into a higher-privilege process.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds write in ANGLE in Google Chrome prior to 151.0.7922.72 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Sandbox escape in Google Chrome's ANGLE graphics layer before 151.0.7922.72 lets a remote attacker who has already compromised the renderer process break out of the sandbox via a crafted HTML page, achieving code execution at higher privilege on Windows, macOS, and Linux desktops. Rated High severity by Chromium with a CVSS 9.6 due to scope change and full CIA impact, though the EPSS probability is only 0.21% (11th percentile). …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires that the attacker has ALREADY compromised the renderer process - this is explicitly stated in the description and is the gating prerequisite; this bug is a sandbox-escape stage, not a first-contact vector. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and must be weighed together. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | A victim with an unpatched Chrome opens an attacker-controlled web page (UI:R) that first exploits a separate renderer vulnerability to gain code execution inside the sandboxed renderer, then uses this crafted content to trigger the out-of-bounds write in ANGLE and escape the sandbox into the more-privileged GPU/browser context. No public exploit is identified at time of analysis, and the scenario depends on chaining with a prior renderer compromise, raising the practical bar. |
| Remediation | Vendor-released patch: update to Google Chrome 151.0.7922.72 or later on the Stable channel (Windows, macOS, Linux) as delivered in the Chrome release advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html - Chrome auto-updates, but confirm by restarting the browser and verifying the version, and push the update via enterprise management (GPO/MDM) to ensure endpoints relaunch. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory your Chrome deployment to identify all systems running versions prior to 151.0.7922.72 using your endpoint management tools. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
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 |
| SUSE Package Hub 15 SP7 | Affected |
Share
External POC / Exploit Code
Leaving vuln.today