Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Network-reachable via a crafted page with user interaction and no privileges; AC raised to H because reliable type-confusion-to-sandbox-escape exploitation is complex, with scope change and total impact.
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
Type confusion in ANGLE in Google Chrome prior to 152.0.7977.65 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
AnalysisAI
Remote code execution in Google Chrome's ANGLE graphics component (versions prior to 152.0.7977.65) allows a remote attacker to potentially escape the browser sandbox by luring a victim to a crafted HTML page. The flaw is a CWE-843 type confusion carrying a 9.6 CVSS score with a scope change, reflecting the sandbox-escape potential. …
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 the victim to load a crafted HTML/WebGL page in an unpatched Chrome build (prior to 152.0.7977.65), so user interaction (UI:R) - navigating to or opening the malicious page - is the key prerequisite; there is no authentication requirement (PR:N). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The signals are partially divergent and should be weighed together rather than in isolation. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker hosts or compromises a web page containing crafted WebGL/graphics content that triggers the ANGLE type confusion, then lures a victim (phishing link, malvertising, or watering-hole) into loading it in a vulnerable Chrome build. When rendered, the corrupted memory operation is leveraged to execute attacker-controlled code, potentially escaping the renderer sandbox as described. … |
| Remediation | Vendor-released patch: update Google Chrome to 152.0.7977.65 or later via the Chrome Releases stable-channel advisory (https://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html), then fully restart the browser so the running process picks up the new binary - Chrome auto-updates but the fix is not active until relaunch. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, conduct inventory of all Chrome installations across organizational endpoints and identify deployment methods (managed or unmanaged systems). …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same technique Memory Corruption
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-65815
GHSA-6vmw-wp49-rcpp