EUVD-2026-65781
GHSA-xfrx-pfwr-x3h9
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Out-of-sandbox code execution implies renderer sandbox escape, warranting S:C; all other metrics align with the network-delivered, user-interaction-required UAF pattern.
Primary rating from Vendor (Chrome).
CVSS VectorVendor: Chrome
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Lifecycle Timeline
4DescriptionCVE.org
Use after free in Accessibility in Google Chrome prior to 152.0.7977.65 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via UI Interaction. (Chromium security severity: High)
AnalysisAI
Use-after-free in Google Chrome's Accessibility component (versions prior to 152.0.7977.65) enables remote attackers to execute arbitrary code outside the browser's renderer sandbox through social engineering. Exploitation requires user interaction with a malicious webpage or crafted UI element, making phishing or malvertising the likely delivery mechanism. …
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 perform UI interaction on a malicious webpage, as specified by UI:R in the CVSS vector - this is the primary practical barrier, as it demands social engineering (phishing, malvertising, or watering hole attack) rather than passive drive-by. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 8.8 (High) score reflects the worst-case impact - full C/H/I/H/A/H - with a network attack vector, low complexity, no required privileges, and only user interaction as a barrier. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker registers or compromises a website and embeds JavaScript or HTML that triggers a specific sequence of Accessibility API events, causing Chrome to access a freed memory region in the Accessibility component. The victim is lured to visit the malicious page via a phishing email or malicious advertisement and performs a UI interaction - such as clicking a button or navigating focus - that triggers the vulnerability. … |
| Remediation | Update Google Chrome to version 152.0.7977.65 or later via the stable channel, as documented in the Chrome Releases advisory at http://chromereleases.googleblog.com/2026/08/stable-channel-update-for-desktop_0256176589.html. … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, audit your Chrome deployment across endpoints and development systems to identify current versions and establish a patch window. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-416 – Use After Free
View allSame technique Use After Free
View allShare
External POC / Exploit Code
Leaving vuln.today