EUVD-2026-50808
GHSA-9vq8-3c74-6rf6
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Delivered via a crafted page (AV:N, UI:R) but requires a prior renderer compromise plus overflow grooming, so AC:H; the sandbox escape crosses a trust boundary (S:C) with full host impact (C/I/A:H).
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
Integer overflow 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)
Articles & Coverage 1
AnalysisAI
Sandbox escape in Google Chrome's ANGLE graphics layer (versions prior to 151.0.7922.72) lets an attacker who has already compromised the renderer process break out of the browser sandbox via a crafted HTML page, gaining high confidentiality, integrity, and availability impact on the host. Rated High by Chromium and CVSS 9.6 due to scope change, it is a second-stage exploitation primitive rather than a standalone initial-access flaw. …
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 an explicit prerequisite stated in the CVE description, making the bug a sandbox-escape (second-stage) primitive rather than a standalone initial-access flaw. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | Signals are mixed and must be weighed carefully. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker first exploits a separate renderer-process vulnerability, for example via a malicious or compromised website the victim visits, then serves a crafted HTML page containing malicious WebGL content that triggers the integer overflow in ANGLE, corrupting memory to escape the sandbox and run code in a higher-privileged process on the host. No public POC is identified at this time, and the multi-stage requirement (renderer compromise plus user visiting attacker-controlled content, per UI:R) increases realistic attack complexity. |
| Remediation | Vendor-released patch: Chrome 151.0.7922.72 - upgrade to 151.0.7922.72 or later on all desktop platforms, which is the primary and complete fix (see the Stable Channel advisory at https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory all Chrome deployments and identify systems running versions prior to 151.0.7922.72. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-190 – Integer Overflow or Wraparound
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